Report runs in preview in VS.net 2003, but not on Report server

I have a report which I have published to my Report server (sql 2000 on
windows 2003). This report runs from my VS.net developers edition preview
page, but once I publish it to my Sql reporting services report server, it
will not run - there is a long delay, then I recieve repeated prompts for
username and password, and then failure.
I am logged in as the same user as on my vs.net.
I have a number of other reports that run correctly on both my development
system and on the report server. I just can not figure out what I have
different in this report or datasource that is causing this issue.
If anyone can help me figure out what permissions I have messed up. I would
appreciate it.
Fred ZilzWhen you run Report as preview in VS.NET, the Report Server is not involved.
So, the preview running fine means you do not have problem to get data (if
the database reeqires logging in).
Therefore, your problem could be that your account cannot log into report
server (do not confuse it with database server, although both may use the
same SQL Server). You could use Report Manager to go to the folder where the
report is deployed, click Properties->Security to see who is allowsed to
browse reports in that folder.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:uaypGQvPFHA.2584@.TK2MSFTNGP15.phx.gbl...
> I have a report which I have published to my Report server (sql 2000 on
> windows 2003). This report runs from my VS.net developers edition preview
> page, but once I publish it to my Sql reporting services report server, it
> will not run - there is a long delay, then I recieve repeated prompts for
> username and password, and then failure.
> I am logged in as the same user as on my vs.net.
> I have a number of other reports that run correctly on both my development
> system and on the report server. I just can not figure out what I have
> different in this report or datasource that is causing this issue.
> If anyone can help me figure out what permissions I have messed up. I
would
> appreciate it.
> Fred Zilz
>|||I have found that the designer and the server handle credentials differently,
are you storing your credentials in the connection string by any chance?
"Fredrick A. Zilz" wrote:
> I have a report which I have published to my Report server (sql 2000 on
> windows 2003). This report runs from my VS.net developers edition preview
> page, but once I publish it to my Sql reporting services report server, it
> will not run - there is a long delay, then I recieve repeated prompts for
> username and password, and then failure.
> I am logged in as the same user as on my vs.net.
> I have a number of other reports that run correctly on both my development
> system and on the report server. I just can not figure out what I have
> different in this report or datasource that is causing this issue.
> If anyone can help me figure out what permissions I have messed up. I would
> appreciate it.
> Fred Zilz
>
>|||Yes, I am storing credentials in the connection string.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>I have found that the designer and the server handle credentials
>differently,
> are you storing your credentials in the connection string by any chance?
> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>|||For security reasons, the report designer will remove credentials from the
connection string (and therefore not store in the RDL connection string on
disk). Consequently, the published report on the server has no credentials
specified and you need to add them e.g. through report manager by updating
the data source information. Credentials specified there are stored
encrypted in the report server metadata database.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
> Yes, I am storing credentials in the connection string.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>|||I have looked at the datasources of a report that works and one that does
not, both have the credentials stored in the metadata database both are
shared data sources, both use the same SQL credentials and both databases
are set with the credentials authorizing database permit and read
permissions. I double checked the security settings on the report server
and both shared data sources and both reports are set with the same security
settings (domain users with browser permissions)
I have tried deleting the reports and redeploying with the same results. I
just can not seem to find what is different between the reports that work
and the ones that don't. They are in fact both in the same report Solution
on my VS.net development station.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:ePJBfILQFHA.4020@.tk2msftngp13.phx.gbl...
> For security reasons, the report designer will remove credentials from the
> connection string (and therefore not store in the RDL connection string on
> disk). Consequently, the published report on the server has no credentials
> specified and you need to add them e.g. through report manager by updating
> the data source information. Credentials specified there are stored
> encrypted in the report server metadata database.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
> news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
>> Yes, I am storing credentials in the connection string.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>>
>|||As a way of trouble shooting I created a new datasource in the same project
as the malfunctioning report. I created a simple report based on that data
source, but used the same connection credentials (SQL) and the same query
string. Deployed this and it works. I then set my malfunctioning report to
the new datasource redeployed and ran - same problem - long pause and then
request for credentials.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:uKFtr1QQFHA.1096@.tk2msftngp13.phx.gbl...
>I have looked at the datasources of a report that works and one that does
>not, both have the credentials stored in the metadata database both are
>shared data sources, both use the same SQL credentials and both databases
>are set with the credentials authorizing database permit and read
>permissions. I double checked the security settings on the report server
>and both shared data sources and both reports are set with the same
>security settings (domain users with browser permissions)
> I have tried deleting the reports and redeploying with the same results.
> I just can not seem to find what is different between the reports that
> work and the ones that don't. They are in fact both in the same report
> Solution on my VS.net development station.
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:ePJBfILQFHA.4020@.tk2msftngp13.phx.gbl...
>> For security reasons, the report designer will remove credentials from
>> the connection string (and therefore not store in the RDL connection
>> string on disk). Consequently, the published report on the server has no
>> credentials specified and you need to add them e.g. through report
>> manager by updating the data source information. Credentials specified
>> there are stored encrypted in the report server metadata database.
>>
>> -- Robert
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
>> news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
>> Yes, I am storing credentials in the connection string.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any
>> chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000
>> on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report
>> server, it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I
>> have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>>
>>
>