Novell Login with SWV 6.1 Errors
Has anyone else experienced any errors when doing a Novell login with a virtual application activated?
Our scenario is with any version of 6.1 (6.1.4108, 6.1.4113, 6.1.5104) and any virtual version of Office (97, XP or 2007).
If one of these applications is active when a user (without admin rights) logs into the workstation using Novell we get some errors on our Active Setup files and some VB6 apps, that ad themselves to the systray, give the invalid picture 481 error. If you wait 10 to 15 seconds and rerun the vbapp, it Launches to the systray just fine.
If you select "workstation only" through Novell and simply log into the domain, everything functions as expected. Also, if you have admin rights and login through Novell, you do not get an error.
We did not see any of these errors/issues when using SVS 2.1.
If you have any thoughts or would like any more information, please let me know. We currently have SVS 2.1 installed on 17,000 nodes and were migrating to 6.1 (which is now on ~900 nodes) and found these issues and have halted the migration.
Thanks
Comments
So Strange
So, I pulled the code for the application that is getting the error and it is simply doing something like:
Private SysTrayIcon As NOTIFYICONDATA
With SysTrayIcon
.uID = 0
.hwnd = Me.hwnd
.cbSize = Len(SysTrayIcon)
.hIcon = Icon.Handle
.uFlags = NIF_ICON
.uCallbackMessage = WM_MOUSEMOVE
.uFlags = .uFlags Or NIF_MESSAGE
.cbSize = Len(SysTrayIcon)
End With
Shell_NotifyIcon NIM_ADD, SysTrayIcon
and dropping the Icon into the users system tray. The app gets a run-time error: 481 "Invalid Picture" error. This would lead me to believe a reinstall of the VB runtime would fix, however, if you wait about 20 seconds after the machine is logged into and then run the app, all is good. THis ap has been running fine for probably 5 years and now we see these strange errors.
The other active setup items that get errors are doing some stuff in HKCU and error out. So, I am at a loss with why some current user items are not available to a non-admin user logging in through the Novell client.
We are going to open a case and see what we can find.
Opening a case is the best
Opening a case is the best course here, there's no real way for me to look at this in the environment I have set up so Support is much better suited to help you.
If a forum post solves your problem please flag is as the solution
Thank
we did open a case and they took a look and are going to get back with us.
There was one other strange thing we found. Were were doing some testing with 6.1 and one of our tests was with the latest primal script. When a non-admin launches PrimalScript for the first time there is an error stating it can't write to HKCU/software/...
Still logged in as non-admin, I can open up HKCU, modify any key and re-launch without error and the new info gets written into HKCU. It is almost as if something is locking down the current user registry, but once we modify it in the OS, the layer can write just fine.
The ability for limited users
The ability for limited users to write to the registry is a know issue we're currently working on a fix for (expect it soon).
If a forum post solves your problem please flag is as the solution
Check network speed
Your symptoms have all the hallmarks of a user profile that has not loaded fully when the various operations you are describing get started.
So my question is:
Do you have roaming user profiles, and if so, do you limit their size?
A few years ago, I was involved in diagnosing a similar problem where apps installs for apps already on the system, we being kicked off as reinstalls when the user logged in. The issue was slow loading of the user registry due to pathetic network performance, causing the system to think that user configurations for the apps were missing, and thus kicking off these reinstalls.
One way to test this is to write a registry key called ZZZ to the HKCU registry (ie HKCU/ZZZ) and then put a value in there.
Then kick off a script from the run key in HKLM which check for this key every 100 milliseconds or so, and records whether the key can be seen.
Once it can be seen, you know that the registry is loaded.
Getting an idea of the time taken for this to happen will quickly reveal whether my hypothesis is correct, or a mile wide of the mark.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I wouldn't think our network
I wouldn't think our network speed would be an issue simply because using 2.1 there are no problems. However, the same machine using the same account with 6.1 gets the errors. Just to make sure, I followed your suggestions:
Added a regkey to HKCU and set the following script to run at startup:
On Error Resume Next
Const ForReading = 1, ForWriting = 2, ForAppending = 8
Set WshShell = CreateObject("wscript.shell")
Set fso = CreateObject("Scripting.FileSystemObject")
Set strFile = fso.OpenTextFile("c:\upapps\HKCU.log", ForWriting, True)
IntCnt = 0
Do While IntCount = 0
RegValue = WshShell.RegRead("HKCU\Software\UP\Loaded")
If RegValue <> "" Then
strFile.WriteLine Now() & ": " & RegValue
WScript.Echo RegValue
intcount = 1
Else
strFile.WriteLine Now() & ": " & "No"
WScript.Echo "No"
End If
WScript.Sleep 100
Loop
strFile.Close
Set WshShell = Nothing
Set fso = Nothing
Set strFile = Nothing
On start up, while the strange errors were happening, the script ran and immediately found the key. So, there is no delay as far as that goes.
I was doing some further testing this morning and on one of the machines there were some reg keys created that I had never seen. Under HKLM 2 keys (with many subkeys) were created, they were called _SWV_LAYER1 and _SWV_LAYER2. I don't know if this is something new in 6.1.5104 or some other something strange.
I have not heard back from our support case yet, but will provide info if we can determine what is going on.
RS
Still Waiting
We are still waiting with support. They were able to setup a Novell server and duplicate the issues, just no fix yet.
Starting to think this may not be ready for a production environment of 18,000 nodes like we have.
Would you like to reply?
Login or Register to post your comment.