Page 1 of 1

Empower 2 Report Publisher Stalling Out

Posted: Tue Jan 05, 2010 7:19 pm
by tcay584
Hello,
I am having a rather odd Empower 2 issue. We just upgraded last week from Empower 1 and are having problems with report publisher taking upwards of 4 minutes to actually pull up a report. We can access systems, process data, background print, pull up instrument methods, processing methods, and method sets super quick, but cannot review report methods or preview reports without waiting what seems like ages. I have to close out using task manager and get a REPORT~1.EXE failure notice. Here's the odd part....the report publisher issue is only happening on some computers. We are not on a Citrix server and the computers are all on the same domain as the empower server. I've called Waters and they're doing all they can, just wondering if anyone else out there has ever had this happen.

Posted: Tue Jan 05, 2010 8:20 pm
by aceto_81
Is this in a stand alone setup, or on a client server enterprise?
Sometimes it takes a bit longer on an enterprise due to network load.
Also the load on the computers is a lot more with Empower 2 compared to Empower 1.

Maybe you can check in your task manager wether it's due to the network traffic or a memory issue?

Ace

Posted: Tue Jan 05, 2010 9:27 pm
by tcay584
It's a client server enterprise. The thing that's driving me nuts is that it seems to be computer specific. I can pull reports up in a snap from my office, but when I'm in the lab it's like frozen molasses. We purchased a new server for this program, so I don't think network traffic is the issue but I'll check the task manager anyway. It doesn't help that I'm not the most computer savvy person in the world :)

Posted: Wed Jan 06, 2010 6:25 am
by aceto_81
Let me know what you find, and then we will search further.

Maybe you can also run tracert to check the connection of the problem pc's to the server, it's maybe a defective router or something.

Ace

Posted: Wed Jan 06, 2010 5:08 pm
by tcay584
Our IT group is so great! They fixed the problem. Apparently, there was a communication switch which was not adjusted when the upgrade occurred, so the new version was being forced to work at the same rate as the old version even though the new server had much more capacity. At least....that's the most I comprehend of it. A group cheer went up from the lab when the fix occurred as now everyone can work at the speed we're used to. Happy Day!