QuoteWerks Knowledgebase Topic (Article ID 6090)

Control File Issues on Terminal Services, Citrix, or Other Thin-Client Environment

This information applies to :

Article ID

July 17, 2019


Are you using the most current release of QuoteWerks?
Version 5.5 Build 4
When running QuoteWerks on Terminal Services, Citrix, or other Thin-Client Environment and not logged in as an Administrator, you receive errors similar to:

Runtime error 339
Runtime error 438
Runtime error 429 cannot create object
File Not Found
Permission Denied
Automation error - the specified module could not be found.

The Terminal Server was not in "Install" Mode when you ran the Node installation or .dll files did not register properly.

Login to the Console as an Administrator then put the server in install mode by typing "change user /install" at a command prompt.

You can then run the NSETUP.EXE file located in the root of the QuoteWerks directory. If this is a Windows Server 2008 server or higher, right-click the NSETUP.EXE and then click "Run as Admin..."

When you are done, make sure to run "change user /execute".

Note: In /install mode, %windir% points to %systemroot% but in /execute mode, %windir% points to %homedrive%\%homepath%\windows.

If UAC is enabled, you may need to give users Read permissions to the \Users\Administrator\Windows folder.

For explicit instructions on updating QuoteWerks in general, please see Respond Article 6039 (https://www.quotewerks.com/kbase/showArticle.asp?articleid=6039).

Additional Notes & Fixes:
If after placing the terminal server into install mode and running the nsetup.exe file, you still receive Run time Error 70 Permission denied or a 339 related error, the control files necessary for QuoteWerks may still be registered/installed in a location that the user does not have access to; typically, the files are installed to a location other than the system32 folder, such as a user specific folder. These files need to be in the Windows\system32 folder, as all users should have access to this directory. A common file to search for is "SCRRUN.DLL"; all QuoteWerks users need access to this file or errors will occur. If this file is not in the system32 folder, it should be moved into the folder and then manually registered. To manually register the file, make sure you're logged in as an Administrator and that the file is indeed located in system32, then in the Start -> Run box type:

regsvr32 C:\Windows\system32\scrrun.dll

A common issue amongst end users is that the system -- at one time -- was not put into /install mode, and the control files ended up in user-specific folders (...\Users\[enduser]\windows). These files will need to be removed, else you will experience extreme difficulties and crashes when trying to utilize QuoteWerks.

If that does not resolve the persistent error, you'll want to run the Medic Utility by going to Start -> Programs -> QuoteWerks 4.0 -> Tools & Information -> Medic Utility and click the File Versions button. If any control files are listed as cannot be found, write those file names down and search for them in Windows. Typically, these files should also be in the system32 folder - if they're not, they should be moved into the system32 folder just like SCRRUN.DLL mentioned earlier. Once the files are moved, repeat the manual registration step above, but change the name of the control file to fit.

If QuoteWerks halts after the user inputs their login information, then the msvbvm60.dll will need to be registered in installation mode as well:

regsvr32 C:\Windows\system32\msvbvm60.dll

There are some instances where this DLL may need to be registered under each end user of the Terminal Server (this is in extreme cases where registering the DLL via /install mode is not working). An easier alternative is to search the registry for "MSVBVM60". Each user will have a registry occurrence of this. Add the "Users" group to Full Control of the folder where the registry key is stored (InProcServer32). This will make for a quicker process for systems with a large amount of end users.

Users must also have full control of this registry key and all entries under it:


Additional registration keys that may need to be opened up are:

HKEY_LOCAL_MACHINE \Software\Microsoft\Windows\CurrentVersion\SideBySide (Full Control)

HKEY_LOCAL_MACHINE\Software\microsoft\windows\currentversion\setup\PnpLockdownFiles (Full Control)

HKEY_LOCAL_MACHINE \Software\Microsoft\Jet\4.0\Engines (Full Control)


HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\WinSock2\Parameters (Full Control)

Another potential fix could be the following:

Include Domain Users to have full control of the C:\Users\Administrator.Domain\Windows directory.

New Search