Problems running recently deployed reports on enterprise server

[llallen1113]

During a package deployment our CNC ran into an error with the deployment server disk space being full. All objects except the report objects appear to have deployed (ie processing optiions, business views, and tables). Our CNC cleaned up the deployment server disk space and resubmited new packages for the objects. However we still are having problems trying to run the reports from the package build. The report changes are not being recognized when run on the server. The reports run correctly when run locally on a client. Has anyone run into this problem before or have any suggestions on how to fix?

Thanks in advance for your help,

Laurie

E1 8.0, SP 22 SQL Sever platform.

 

[Joel]

We had a similar issue where our deployment server was out of space and the client pkg went into error. We cleaned up the DS and did a re submit, however the package continued to go into error . Later it was found that the TAM specs had got corrupt. We then deleted the package and built one from scratch which did the trick.
I would suggest that you do a new package with the objects, a full build will be better. Has there been any dd changes ? If yes then a service bounce is needed.

 

[brother_of_karamazov]

See if you have, on the enterprise server, any cl.exe or builddll.exe processes running. If you do, you are going to have to either kill all of those processes and bounce the services or (easier) reboot the box. Then you should build another (different) package and deploy.



[ QUOTE ]
During a package deployment our CNC ran into an error with the deployment server disk space being full. All objects except the report objects appear to have deployed (ie processing optiions, business views, and tables). Our CNC cleaned up the deployment server disk space and resubmited new packages for the objects. However we still are having problems trying to run the reports from the package build. The report changes are not being recognized when run on the server. The reports run correctly when run locally on a client. Has anyone run into this problem before or have any suggestions on how to fix?

Thanks in advance for your help,

Laurie

E1 8.0, SP 22 SQL Sever platform.

[/ QUOTE ]

 

[llallen1113]

Thank ya'll for the responses. We will check into these areas and let you know what we find.

Thanks again!

Laurie

 

[llallen1113]

We were able to resolve the problem. It appears that our last 2 full package builds did not complete sucessfully. The only way we knew this was by reviewing the svrbuild logs. The last full package build was deleted and a new full package build created and deployed. Problem resolved and all report changes implemented. Thanks again for your help.

Laurie