OInsight doesn't start after adding TS app compatibility flag in Registry (OpenInsight 32-bit Specific)
At 21 OCT 2005 09:06:35AM Dave Parsons wrote:
We have an application running under OpenInsight for Workgroups 4.1.2. After moving this to Citrix I have found that the users get lots of errors and performance is really slow. I had been been advised by the vendor to add 2 regkeys for the application compatibility so that TS returns the username rather then the hostname as the stationid. When I set these regkeys thoough, oengine fails to start. the splashscreen briefly appears and then the application terminates.
The regkeys added are:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\OENGINE
"Flags"=dword:00000018
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\OINSIGHT
"Flags"=dword:00000018
Does anyone have any ideas?
At 21 OCT 2005 10:37AM Ray Chan wrote:
Dave,
Vendor? Is Citrix, the vendor that advised you?
FWIW, we have run OI on Citrix/TS and have never made any change to the registry setting to make it work. How many users are you running on Citrix?
I'm not an expert on registry so I'm curious on its purpose. Also, maybe someone else will respond. If you put the registry setting back, does OI start?
Oh btw are you using the OI network services?
Ray Chan
At 21 OCT 2005 12:05PM Dave Parsons wrote:
Hi Ray,
The software is called YOIS - youth offender IS by Social Software (a UK crowd). It was them that recommended the regkey to me. Perhaps it's the way that they've written their software that they use the hostname/stationid as some sort of unique key?
There are only about 40 concurrent users over 4 dedicated servers (at the moment) so loading certainly isn't an issue.
The first user gets in fine and fast but subsequent users get all the problems.
If the regkey is removed or changed to not apply to 32bit apps then OI does start.
I'm not sure about OI network services as my sum total knowledge on OI is what I've found out looking at this problem
Dave
ps - I'm just finishing for the day so hopefully more input Monday.
At 27 OCT 2005 04:05AM Colin Rule wrote:
This is resolved by getting the application to recognise a unique user, we have done this by appending the TIME to the Station Id
We have a switch that performs this
WRITEV "SET_STATION*ICEPAC" ON SYSENV,"ENV_ICEPAC",32 ELSE NULL
Our application is called ICEPAC, and SET_STATION is a stored procedure.
By writing the entity name to attr 32 of the ENV item it makes the station id unique and resolves the speed issue.
FUNCTION Set_Station (Flag, Station)
* Sets the Station ID
* Required for Terminal Server
*
Station=FIELD(STATION,"-",1):"-":TIME()RETURNEND