I think the problem you are talking about is that you are trying to do an installation of CR onto a web server and the server team isn't letting you properly install the CR software. When you install CR, there are A LOT of changes made to your computer and this includes adding registry entries used by CR configuration. What you are attempting to do is just copy the DLLs onto the server and get CR to run. Unfortunately, this isn't possible b/c you also need to add configuration entries to the registry and this can only be done by running the CR installation. Thus, you need to get your server team to review the CR installation package and test it so that they feel comfortable installing it on the production server.

Are you actually running the MSI on the web server? This is necessary to make sure all the DLLs are registered on the server and that the misc. Windows registry entries are made.

My first thought is that this is a permission problem. I would check the folders to make sure that the ASPNET account has access to the folders where your reports are saved. Also, make sure you have read/write permission to the temp folder that CR uses. This causes many people problems b/c they forget that when CR tries to open a report that it creates a copy of that report in the temporary folder and uses that for processing the report passes. Since web servers are locked down pretty securely, it might be a challenge to track everything down and set the correct permissions.