environment variable problem after 9.x upgrade

  • Thread starter Thread starter sanweb
  • Start date Start date
S

sanweb

Hello,

We have been running for several years and have upgraded 2x in the past without issues but after trying to upgrade from 8.x to 9.x our main database application will not run properly. I found that for some reason the users environment variables are not being passed to the application anymore. The command line that starts our database requires a user specific .ini file to be loaded from a folder in the users documents folder. This .ini file assigns the workstation ID for the user that is logged in. Here are the published application settings:

Target: J:\GJCWIN\sbbwin.exe
Start In: %userprofile%\GJCWIN\data
Parameters: %userprofile%\GJCWIN\jonas.ini GJC00

We are running 2x on a Windows 2003 server using a workgroup instead of a domain. All of our workstations are WinXP Pro.

After upgrading to 9.x when a user tries to launch the application it now seems like it is being launched in the context of the Administrator and is getting the .ini file from the administrators folder because the application shows all users running under the same workstation ID instead of a unique ID for each user like it is supposed to. I had to downgrade back to the 8.x version until I find a solution for this issue. Any ideas would be greatly appreciated.

Thanks,
Dan
 
I have a similar application that also uses a .ini file in the usersprofile but after upgrading from 8.1 to 9.0 build 1051 i got the same problem you are experience.
In my case the application complains that the .ini file is write protected since it for some reason in v9.0 appears to be using the .ini file in the C:\Windows on the 2X TS instead of the ini file in the usersprofile in our case H:\Windows
I was also forced to go downgrade to 8.1and then it works without any problem again.
I have opened a support ticket on this problem, and its nice to see that I'm not the only one experience this strange behavior in v9.0
 
Nobrell,

Thanks for replying with your experience. I also just submitted a support ticket and I will let you know if/when I have a resolution. If you have any new information please post back. Maybe someone else will jump in and post some ideas in the meantime.

Thanks,
Dan
 
I think that I have the same problem. After upgrading to v9.x any app that depends on a mapped drive fails to work correctly.
Here is what I believe is happening. I have a group policy set to Run logon scripts synchronously. This prevents applications from starting and trying to use a mapped drive that has not yet been mapped by the logon script or logon process. v9.x seems to circumvent this GPO and is launching applications before the logon process has finished. This causes apps that rely on mapped drives to not work correctly.

I hope that there is a quick resolution to this and somebody else can confirm this.

Thanks,
Brian
 
We're having the exact same problem as Brian. We're also having problemes with lagging windows on published applications when users are connectiong to 2003 r2 64bit ts, works on 2008 r2 64bit. The uses also sees every printer installed on ts not just the ones belong to their session.

With this and the previous posts in mind it seems quite clear that for some reasons users are getting semi logged on as administrators or something.
 
For anybody having problems with apps running before a mapped drive is ready here is a vbscript I got from 2x support and modified. Change the drive and application to meet your needs.


'**************Start Code**************
' Application Launching Script Version 1.1

Sub Delay(DelaySeconds)
SecCount =
Sec2 =
While SecCount < DelaySeconds + 1
Sec1 = Second(Time())
If Sec1 <> Sec2 Then
Sec2 = Second(Time())
SecCount = SecCount + 1
End If
Wend
End Sub

'Initialize File System Object
Set filesys = CreateObject("Scripting.FileSystemObject")
s=0

Do Until filesys.DriveExists("H:") 'Check for mapped drive
s=s+1
Delay 1
Loop

If filesys.DriveExists("H:") Then 'Double check drive is mapped
Dim objWshShell
Set objWshShell = CreateObject("WScript.Shell")
Delay 3
objWshShell.Run "C:\Progra~1\Micros~1\Office12\Outlook.exe" 'Run application
Set objWshShell = nothing
End If
TotalTime = s + 3

'WScript.Echo("Total seconds to waiting for mapped drive = ") & TotalTime 'Debugging info un-comment to use

'**************End Code**************
 
You must log in or register to reply here.
Back
Top