Installation of 7.6 SR3 giving issues

This is my second attempt at trying upgrade to SR3. Upon completing the installation, no existing folders are able to be opened. Also, no blank forms are able to be launched (whether from existing maps or new maps...I tried both). What happens is that the rectangular status bar just continues to tick. No events are logged in the event viewer.

Also, when logging out, I'm givin an error. I've attached a screen shot using IE7. I've noticed that there are two hotfixes for SR3, but from the release notes it doesn't seem that they will fix this problem.

Anybody encounter this issues? Suggestions? Thanks in advance!

Find more posts tagged with

BPM

Comments

achopra

Did you run the eWorkProcedures.sql on the Metastorm database and then restart the Engine?

Rafael Pargas

I have and even re-ran them to be sure before writing this post. Still encountering issues.

Chuck Gembarowski

Dastorm - I think that you should contact the Help Desk for some assistance. I think that it would be best to have the Help Desk do a remote session with you.

Best Regards,

ChuckG

Rafael Pargas

Thanks ChuckG. I'll do so.

On a similar note, does anyone know if I were to re-run the SR3 installation through the wizard again, will I encounter any problems? The documentation states that I would be unable to roll back to SR2, but I'm curious what will happen if I were to try and run the SR3 installation/scripts once more or if I will be making more problems.

Jonathan Caley

Sorry to resurrect this old post, but did this ever get resolved? I'm having the same issue. I've narrowed it down to the engine, not the database. Three engines pointing at the same SR3 database, but only two of them upgraded. The baseline 7.6 engine works fine, but the SR3 ones do not allow items to be opened and will not sort using the To Do/Watch List left panel.

Paul Denton

The DB can on be in one of two states, configured for 7.6.3 or not (possibly configured for 7.6.0)...

If you have a 7.6.0 engine running against the DB and a 7.6.3 engine failing to work against the same DB it would suggest that the DB is setup for 7.6.0.

When running the eworkProcedure.sql script it is important to use the one off the engine server after the SR3 update is applied. It has been updated, running one from the install disks will not work.

I know it is stating the obvious but we do see it fairly frequently...

Paul...