Sunday, March 11, 2012

Deploying Reports

this is about two related issues...
We tried to deploy by backing up the ReportServer DB on my XP dev box and
restoring over an existing ReportServer DB on a Server 2003 box. After the
restore, when trying to go to /localhost/reports we got "login failed for
'NT AUTHORITY\NETWORK SERVICE'. We then added that user to the ReportServer
Database. Then we got 'Cannot read ReportServer DB. Found Version unknown
expected Versions C.0.8.40.
So the first question is what went wrong?
The second question is: How are we supposed to deploy reports from an XP dev
box to a Server 2003 box? It can't be database backups and restores - it
must be by report but I can't find it in the docs. Can you point this out
in the docs or tell me how?
--
Regards,
Gary BlakelyHi Gary,
Thank you for your posting!
For the first issue, I think the root cause is that your Report Server
database is not match the Reporting Services binaries. The binaries are SQL
2005 and I wonder what's your Report Server databases in the dev box. If
it's SQL 2000, please follow the article to migrate the report server
database to SQL 2005:
If not, please make sure the Reporting Services is the same with the
service pack.
If your reporting services on your dev box is SQl 2005 SP1, I think you
need to upgrade your SQL 2005 on your server box to SP1 and then restore
the database.
For the deploy issue, as I mentioned above, you could use the backup and
restore to move all the reports to another server. But, the reporting
services should be the same.
Also, I think the best way for you is keep the report design project and
use the project to deploy the reports again.
Hope this will be helpful! If you have any questions or concerns, please
feel free to let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Wei,
All boxes are using ss2005.
I think that restoring over the ReportServer db on the target machine is not
a good idea because several programers will be deploying reports to that
machine and we can't wipe out work already on the target reporserver.
Can I deploy to another Server on the network. Seems that should be the way
to deploy.
But a second issue is the difference between XP and Server 2003. XP uses
MACHINE\ASPNET and Server2003 uses 'NT AUTHORITY\NETWORK SERVICE'. If we
don't use restore this should not be an issue because we are just deploying
reports. no?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:8LOq3oAnGHA.4632@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> Thank you for your posting!
> For the first issue, I think the root cause is that your Report Server
> database is not match the Reporting Services binaries. The binaries are
> SQL
> 2005 and I wonder what's your Report Server databases in the dev box. If
> it's SQL 2000, please follow the article to migrate the report server
> database to SQL 2005:
> If not, please make sure the Reporting Services is the same with the
> service pack.
> If your reporting services on your dev box is SQl 2005 SP1, I think you
> need to upgrade your SQL 2005 on your server box to SP1 and then restore
> the database.
> For the deploy issue, as I mentioned above, you could use the backup and
> restore to move all the reports to another server. But, the reporting
> services should be the same.
> Also, I think the best way for you is keep the report design project and
> use the project to deploy the reports again.
> Hope this will be helpful! If you have any questions or concerns, please
> feel free to let me know.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Gary,
Thank you for the reply.
Deploy the report from your Visual Studio will be OK. The user is not a
issue. You could deploy the report from your designer to the server.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

No comments:

Post a Comment