Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts

Friday, March 30, 2012

Puzzled by installation error.

I have tried installed several times the SQL Server 2005 Express (Standard or Advanced Services) on my XP SP2 system and all failed.

The error messages are all about the Secure Socket Layer certificate and provider, either cannot find, create valid SSL certificate or the authentication provider is not trust (actually I don't know any of this and where to find them). I am learning at home the SQL Server and not going to do a website. Why I need a SSL? Or if it is really necessary, how do I obtained one?

I installed IIS (supposedly 5.0 since I have XP SP2), is this related? How to install without IIS?

Or do I need a Server OS?

Turn of the SSL on the default website (where Reporting Service will be installed) and you should be able to install the whole thing easily. Afterwards you can turn on SSL again on the default website.

HTH, Jens K. Suessmeyer.


http://www.sqlserver2005.de

|||

How to turn off SSL? In SQL Express setup or IIS setting in MMC?

My IIS setting has a default SSL port 440 but I cannot change it.

Puzzled by installation error.

I have tried installed several times the SQL Server 2005 Express (Standard or Advanced Services) on my XP SP2 system and all failed.

The error messages are all about the Secure Socket Layer certificate and provider, either cannot find, create valid SSL certificate or the authentication provider is not trust (actually I don't know any of this and where to find them). I am learning at home the SQL Server and not going to do a website. Why I need a SSL? Or if it is really necessary, how do I obtained one?

I installed IIS (supposedly 5.0 since I have XP SP2), is this related? How to install without IIS?

Or do I need a Server OS?

Turn of the SSL on the default website (where Reporting Service will be installed) and you should be able to install the whole thing easily. Afterwards you can turn on SSL again on the default website.

HTH, Jens K. Suessmeyer.


http://www.sqlserver2005.de

|||

How to turn off SSL? In SQL Express setup or IIS setting in MMC?

My IIS setting has a default SSL port 440 but I cannot change it.

Wednesday, March 21, 2012

purge .txt log files

SS2005, SP2
Anyone has a quick way of deleting log files for db maint. plans? By default
they are text files created under the LOG directory. Tired of googling for
it 'cause there arn't many posts...I believe this is in one of the maint tasks.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
> SS2005, SP2
> Anyone has a quick way of deleting log files for db maint. plans? By default
> they are text files created under the LOG directory. Tired of googling for
> it 'cause there arn't many posts...
>|||Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the
job. They simply cleanup the actual backup files, or the backup/restore
history tables in msdb. I want something to clean up the log files otherwise
they keep accumulating...
I can write a homegrown process to handle this. But I'd be amazed that
there isn't anything out of the SSIS box that can do this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>I believe this is in one of the maint tasks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...|||> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job.
I see, I though this was part of the "standard process". But Maint Cleanup Task isn't limited to
deletion of backup files. Did you try to add one more such task for deletion of the .txt files?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job. They simply
> cleanup the actual backup files, or the backup/restore history tables in msdb. I want something to
> clean up the log files otherwise they keep accumulating...
> I can write a homegrown process to handle this. But I'd be amazed that there isn't anything out
> of the SSIS box that can do this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By default they are text files
>> created under the LOG directory. Tired of googling for it 'cause there arn't many posts...
>|||Yes, I tried but it didn't work. I also tried to fool the manit plan to
purge regular text files that were renamed just like the backup files. It's
smart enough to know what files are real backup files and what are not, and
only delete REAL backup files. interesting! Fortunately those txt log files
are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big
deal.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does
>> the job.
> I see, I though this was part of the "standard process". But Maint Cleanup
> Task isn't limited to deletion of backup files. Did you try to add one
> more such task for deletion of the .txt files?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does
>> the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...
>>
>|||I'm a bit confused here. When I open the "Maintenance Cleanup Dialog", there's an option to delete
"Maintenance Plan text reports". Perhaps this was introduced with sp2? Or did you try it and it
didn't work (of so, you should file a bug on http://connect.microsoft.com/sql)?.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
> Yes, I tried but it didn't work. I also tried to fool the manit plan to purge regular text files
> that were renamed just like the backup files. It's smart enough to know what files are real backup
> files and what are not, and only delete REAL backup files. interesting! Fortunately those txt log
> files are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big deal.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job.
>> I see, I though this was part of the "standard process". But Maint Cleanup Task isn't limited to
>> deletion of backup files. Did you try to add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job. They simply
>> cleanup the actual backup files, or the backup/restore history tables in msdb. I want something
>> to clean up the log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that there isn't anything out
>> of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By default they are text
>> files created under the LOG directory. Tired of googling for it 'cause there arn't many
>> posts...
>>
>|||Tibor, that's a good catch. I overlooked it.
However, i still was unable to get it to work. I have tried it on one
default instance and two clustered instances, with a separate cleanup task
and proper length of days /weeks to purge - log files are not deleted.
A similar bug was logged in the Feedback list earlier this month and MS
marked it as resolved. The ticket wished to build both purging backups and
log files into one interface. So from the wording, it seems someone has
successfully gotten it worked.
I'll try more instances in case it's just a permission issue. Since I've
already had my purge routine in place, it won't be an issue any more even if
it doesn't work. but I'll try to send them a comment on this.
Thanks for your time on helping this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
> there's an option to delete "Maintenance Plan text reports". Perhaps this
> was introduced with sp2? Or did you try it and it didn't work (of so, you
> should file a bug on http://connect.microsoft.com/sql)?.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>> Yes, I tried but it didn't work. I also tried to fool the manit plan to
>> purge regular text files that were renamed just like the backup files.
>> It's smart enough to know what files are real backup files and what are
>> not, and only delete REAL backup files. interesting! Fortunately those
>> txt log files are tiny (1 or 2 kbs each) so leaving them uncleaned really
>> isn't a big deal.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job.
>> I see, I though this was part of the "standard process". But Maint
>> Cleanup Task isn't limited to deletion of backup files. Did you try to
>> add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...
>>
>>
>|||> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
This is what I also tend to do. When Maint plans don't do what you want, do it yourself... :-)
Let us know if you find out anything more about this... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eOtl7aDuHHA.1204@.TK2MSFTNGP03.phx.gbl...
> Tibor, that's a good catch. I overlooked it.
> However, i still was unable to get it to work. I have tried it on one
> default instance and two clustered instances, with a separate cleanup task
> and proper length of days /weeks to purge - log files are not deleted.
> A similar bug was logged in the Feedback list earlier this month and MS
> marked it as resolved. The ticket wished to build both purging backups and
> log files into one interface. So from the wording, it seems someone has
> successfully gotten it worked.
> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
> Thanks for your time on helping this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
>> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
>> there's an option to delete "Maintenance Plan text reports". Perhaps this
>> was introduced with sp2? Or did you try it and it didn't work (of so, you
>> should file a bug on http://connect.microsoft.com/sql)?.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>> Yes, I tried but it didn't work. I also tried to fool the manit plan to
>> purge regular text files that were renamed just like the backup files.
>> It's smart enough to know what files are real backup files and what are
>> not, and only delete REAL backup files. interesting! Fortunately those
>> txt log files are tiny (1 or 2 kbs each) so leaving them uncleaned really
>> isn't a big deal.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job.
>> I see, I though this was part of the "standard process". But Maint
>> Cleanup Task isn't limited to deletion of backup files. Did you try to
>> add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>>> SS2005, SP2
>>>
>>> Anyone has a quick way of deleting log files for db maint. plans? By
>>> default they are text files created under the LOG directory. Tired of
>>> googling for it 'cause there arn't many posts...
>>
>>
>>
>

Monday, March 12, 2012

Pull Merge constantly have all the same conflicts

Hello.

Let me describe first my replication setup:

- SQL Server 2005 SP1 (SP2 coming soon)

- Approximately 35 remote users (Salesrep laptop) using Pull Subscriptions

- Merge (Bi-Directional) (8 articles - tables only)

- Merge (Uni-Directional) (5 articles - tables only)

- Transactional (5 articles - tables only)

Users receive data based on their territory #, therefore they receive their customers sets of data. It happens that customer change from one territory to another but not frequently. When it happens, so far so good, the data is redirected to the new salesrep using the model we configured (Territory table with SUSER_NAME() to filter the data).

Ok, here's my problem. Since a while, I can see in the replication monitor that some users seems to log the same conflict again and again (Merge process). I mean, checking the history for many subscribers, there is always the same number in the "Conflict" colums.

As an example:

- Merge completed after processing 18 data change(s) (4 insert(s), 14 update(s), 0 delete(s), 31 conflict(s))

- Merge completed after processing 27 data change(s) (10 insert(s), 17 update(s), 0 delete(s), 31 conflict(s))

- Merge completed after processing 20 data change(s) (5 insert(s), 15 update(s), 0 delete(s), 31 conflict(s))

and so on...(Those are only 3 historical entries for a single subscriptions but there are many like that, always with the same count of conflict - vary per user). It appears to me that the same conflicts come over and over.

The thing is that if I decide to reinitialize a subscription, conflicts will disappear, therefore I know that it is not a process on the server that keeps changing the data; anyway, even if it was, changes would be applied on the subscription because the server always win in my setup.

Any idea what should I do with this? Any help would be greatly appreciated.

Thanks.

Can you use the conflict viewer to see what these conflicts are to see if they make sense to you?|||

Woops, I feel like an idiot now Tongue Tied

Thanks for opening my mind!

Wednesday, March 7, 2012

Publisher SP1 Subscriber SP2 ?


I have a clustering between Server A and Server B. There is a clustered SQL Server installed.

Server A is a primary node(oltp production server) and Server B is a secondary node.

i've set up transactional replication betw serer A and B. Server A is Publisher and Server B is subscriber. B also has a distribution database. I use serve B for all the reporting purposes.

Currently both servers have sp1.

Now i want to apply sp2 to the server B first since i use it for reporting purposes (just to make sure there are no issues and then after some days i want to apply sp2 on server A which is my prodction oltp server)

So when i apply sp2 on server B , my publisher will have SP1 and subscriber (& distributor) will have sp2. Will this cause any issues with replication?

Any help would be appriciated.

Thanks

No, the correct order it to update the distributor first, then the publisher and finally the subscibers. It sounds like you are doing things correctly.

I am a little confused by your clustering topology - I take it you have a multi-instance (active active) topology?|||
Thanks so much for the reply.

Actually i have active passive clustering. Server A is primary and Server B is secondary. If something goes wrong with A, it fails over to B but not a vice-versa. Server A is my production oltp server.

On server B i also installed a named instance (standalone instance not the clustered instance) which i am using for all the reporting purposes.

For replication, I am replicating server A database articles to the named instance on Server B. And this named instance is also acting as its distributor.

So

Server A (Default Instance & Clustered):- Publisher

Server B\Instance Name (standalone instance): Subscriber as well as the distributor

So if I apply SP2 on the named instance of Server B, i will be upgrading distributor as well as Subscriber (both at the same time.) And after some days i am planning to apply SP2 on the cluster which will upgrade my production oltp in the cluster.

I hope this will clear your doubts.

Please let me know if there are any issues with what i am doing as i explained above.

Thanks

|||I am unaware with any issues surrounding this. It should work.|||Thank you so much.

Publisher SP1 Subscriber SP2 ?


I have a clustering between Server A and Server B. There is a clustered SQL Server installed.

Server A is a primary node(oltp production server) and Server B is a secondary node.

i've set up transactional replication betw serer A and B. Server A is Publisher and Server B is subscriber. B also has a distribution database. I use serve B for all the reporting purposes.

Currently both servers have sp1.

Now i want to apply sp2 to the server B first since i use it for reporting purposes (just to make sure there are no issues and then after some days i want to apply sp2 on server A which is my prodction oltp server)

So when i apply sp2 on server B , my publisher will have SP1 and subscriber (& distributor) will have sp2. Will this cause any issues with replication?

Any help would be appriciated.

Thanks

No, the correct order it to update the distributor first, then the publisher and finally the subscibers. It sounds like you are doing things correctly.

I am a little confused by your clustering topology - I take it you have a multi-instance (active active) topology?|||
Thanks so much for the reply.

Actually i have active passive clustering. Server A is primary and Server B is secondary. If something goes wrong with A, it fails over to B but not a vice-versa. Server A is my production oltp server.

On server B i also installed a named instance (standalone instance not the clustered instance) which i am using for all the reporting purposes.

For replication, I am replicating server A database articles to the named instance on Server B. And this named instance is also acting as its distributor.

So

Server A (Default Instance & Clustered):- Publisher

Server B\Instance Name (standalone instance): Subscriber as well as the distributor

So if I apply SP2 on the named instance of Server B, i will be upgrading distributor as well as Subscriber (both at the same time.) And after some days i am planning to apply SP2 on the cluster which will upgrade my production oltp in the cluster.

I hope this will clear your doubts.

Please let me know if there are any issues with what i am doing as i explained above.

Thanks

|||I am unaware with any issues surrounding this. It should work.|||Thank you so much.

Saturday, February 25, 2012

Publish A Report Services Report to SharePoint

OK... I'm running out of things to try.

I have SQL Server 2005 SP2 installed and Reporting Services Addin configured. I am trying to publish a report from BIDS to SharePoint... but a box continues to pop up asking me for credencials.

What am I doing wrong? I have reviewed all the web.config files as per an earlier post referenced, but I only see one entry in the config file for the location tag. However, I did see this tag in two config files... not certain if that is something I should be concerned with?

I'd really like to just get a sample report up on the Sharepoint Server so I can move forward.

Can anyone help?

You can always just upload the .RDL file directly into SharePoint using the SharePoint web UI. When RS integrates with SharePoint, we tell SharePoint to handle .RDL files as Report Server items, and it doesn't really matter whether they get into SharePoint through Report Designer, or through SharePoint web UI.

I'm afraid I can't help with the Report Designer issue. I'll pass this on to someone who might know about it.

|||Please check Inetpub\wwwroot\wss\VirtualDirectories\80\web.config|||

What am I looking for when I go to Inetpub\wwwroot\wss\VirtualDirectories\80\web.config?

It does have one entry for location path=" _vti_bin...." as previously mentioned, a number of the web config files have this entry in it... but only once per file.

And just to clarify... I am using BIDS trying to deploy the report. The version of Visual Studio is: 8.0.50727.42.

|||I did that and surprisingly it worked... how does the report connect to the database? I did not upload or create a datasource? Well... actually I had manually created one in SharePoint in another library, but subsequently deleted it. The report still runs?|||Actually... I'll answer my own question... the first report used a custom data source... so that is why it worked. The second used a shared data source... it failed until I created the shared datasource|||

I've been running into this, too. Brian Welcker's blog solved it.

http://blogs.msdn.com/bimusings/archive/2007/02/07/reporting-services-login-dialog-appears-when-deploying-to-moss-wss.aspx