Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 15 FEB 2011 07:13:00PM Gerry Van Niekerk wrote:

Installed the Upgrade OK

Then ran RUN_O4WUPGRADE from Monitor

From Browser

1. Cant login - not a valid user, user still in O4WPERMS Record

2. Cant access Config records as it want to log me in first

3. Clicked on users under o4w maintenance, and got the following error

SYS1000: Error loading program "O4WI_DOLOGIN".

Checked and record doesn't exists in sysobj.

When I run another procedure from Browser that doesn't use the login it still executes OK

Regards,

gerry@csbmgmt.com


At 16 FEB 2011 03:28PM Gerry Van Niekerk wrote:

Furthermore to the above..

I have reinstated version 92 from backup (only root files NOT updated o4wfiles)

Tested o4w and all works,

Redid the upgrade to ver921

Had to change version number on o4wconfig file for the app we are using to 1.1 as it was still 1

Still no luck, then tried to copy the CFG_O4W to the app config record as there is some added items in the record not in the app config record.

and still the same problems where we cant log in to o4w in 921

Anything else to look at?

Regards,

gerry@csbmgmt.com


At 16 FEB 2011 10:32PM Bryan Shumsky wrote:

Hi, Gerry. Sorry to hear you've been having trouble with the upgrade. This is a bit of a complicated one - more so than usual, as we need to run some post-upgrade processes to bring all the new O4W 1.1 goodness to existing users.

I don't know what state your O4W is currently in, so I don't know if the best thing to try is to go _back_ to 9.2, and re-run the upgrade to 9.2.1. Once the upgrade is complete, please:

1. From within the browser, go to the O4W Configuration Maintenance screen _first_. Click on the scripts tab, and configure your script source and themes. Be sure to click on the "Save Changes" button. This will update your configuration record to O4W 1.1. You must do this for _each_ application you have O4W defined for (if you have more than one);

2. From the System Monitor, in _each_ application you have O4W defined for, you must run the O4WUPGRADE procedure by typing "RUN O4WUPGRADE". This will update your security settings, and reconfigure other O4W components for O4W 1.1

After trying these steps on your newly-upgraded 9.2.1, please let me know if you can then access O4W.

Thanks,

- Bryan Shumsky

Revelation Software

At 17 FEB 2011 01:52AM Gerry Van Niekerk wrote:

Hi Bryan,

Have already done all your recommendations earlier today

Restored prev version.

Tested to see if I can log in, answer is Yes

Reinstalled upgrade.

Same problem.

Can't get to resave the script as the system wants me to log in first..

If you email me your email address I will send you the online ip address to see the message.

We use server2008 r2 which shouldn't make a difference.

and Firefox

In Firefox we get a message when you click on users sys1000 error loading o4wi_dologin

This proc doesn't exist and you may create it on the fly but its not in sysobj file.

Thanks

Regards,

gerry@csbmgmt.com


At 20 FEB 2011 04:57PM Gerry Van Niekerk wrote:

All systems now working again.

Thanks to Bryan S…

I redid the 921 upgrade and would like to note as follows:

1. Run the o4wupgrade procedure in SYSPROG FIRST then run the o4wupgrade in all other Apps.

2. Make sure you clear your browser History especially the cache, as this also caused some problems.

Thanks again for the help

Regards,

gerry@csbmgmt.com

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/9dcec994b9652d01852578390001310f.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1