You may run into an error deploying SSRS reports when you move an instance / database to another environment and / or domain. We do this often when developing on our servers and moving the entire instance to a customers site (usually the first move of the Pilot instance during the implementation). The user that it throws as an error for is the AOS service name from the source system. I found that if you look at the data in the table "SysServerSessions" after you move the environment, the AOS information from the source system is still there. In SQL you can remove the invalid server sessions and reploy the reports without error.christmas decorations Best regards, Kevin
