Problem attaching volumes with indexed tables (OpenInsight 32-Bit)
At 23 MAY 2003 07:26:39PM Jim Mabey wrote:
My data files are located on same server as my web server.
I'm running a named engine with a single persistant engine on this server. OI V4.1.3, windows 2000 service v2.1.
My problem is that if I start the engine on the server first, then I can't attach volumes that have indexed tables when running a separate session of OI from a client station.
If I start a session from a client workstation first, then my copy on the server (started after the client session started) can't attach a volume that has indexed tables.
Any tips?
Thanks,
Jim
At 27 MAY 2003 07:31AM Sean FitzSimons wrote:
Jim,
Are the engines being started using desktop shortcuts?
Sean
At 31 MAY 2003 04:06PM Jim Mabey wrote:
Sean, thanks for your help sorry for the delay in getting back to you - I was out for a few days.
Yes, I am running OINSIGHT on the server as I mentioned in a previous post. Actually I had asked if you could let me know how I can get around having to load OINSIGHT on the server.
I tried running OENGINE /SN=AMMS1 /AP=STAFFING /UN=STAFFING /PW=xxxx
The engine starts up on the server, but I get a
"OECGI RevCreateQueue failed, error 1003." from the client browser. I have the server name set in the registry along with application name, etc…
One thing I mentioned in a previous post is that when I view engine info, it shows SYSPROG, SYSPROG even though I specified the /UN=, etc…
I used the info you provided to me on 05-19-03, including:
"ServerName - any name you would like to give. The same name must be placed into the SN command line parameter on your OpenInsight shortcut."
Thanks again for your help,
Jim Mabey
At 05 JUN 2003 03:05PM Wayne Shepard wrote:
Error 1003 is a failure while attempting to log in. In our case here, the problem was that we didn't have username defined in the registry. That doesn't seem to be the problem at your place. The fact that the first user is able to log in with no problem from whichever side it's on indicates to me that your license is only set up for one user. Therefore the second user always fails. You might try logging in manually on both the server and the client to see if you get an error message you can use.
Wayne