Skip to content
Incorrect temp path showing up on deployed workstation
Got a problem with Viscosity or need help? Ask here!
Hi Everyone,
I installed Version 1.5.6 onto a 64-Bit Windows 7 Pro SP1 workstation with two drives.
The system's Windows Temp directory is D:\WINTEMP
Once I debugged my client/server configuration, I exported the connection to a .visz file.
I had a coworker install 1.5.6 onto his workstation (another 64-bit Windows 7 Pro SP1 workstation) and import the files that I exported.
When he tries connect to the OpenVPN server, a message appears, after about a minutes, saying it is disconnected.
The status windows shows....
Version 1.5.6 (1340) - Windows 7 Pro SP1 x64
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid if this is a Custom Gateway.
The log file shows ...
Jun 01 11:31:41 AM: State changed to Connecting
Jun 01 11:31:41 AM: Viscosity Windows 1.5.6 (1340)
Jun 01 11:31:41 AM: Running on Microsoft Windows 7 Professional
Jun 01 11:31:41 AM: Bringing up interface...
Jun 01 11:31:42 AM: Checking reachability status of connection...
Jun 01 11:31:43 AM: Connection is reachable. Starting connection attempt.
Jun 01 11:31:43 AM: Options error: Temporary directory (--tmp-dir) fails with 'D:\WINTEMP\': No such file or directory
Jun 01 11:31:43 AM: Options error: Please correct these errors.
Jun 01 11:31:43 AM: Use --help for more information.
The problem is this workstaton has no D: drive installed. It is a single drive system.
I checked the registry and found, under one of the viscosity entries, the D:\WINTEMP\ entry. I tried changing it to the actual Windows Temp directory and rebooted the workstation.
The same error came up and the Viscosity temp directory still pointed to the nonexistant D:\WINTEMP\ directory.
Does anyone know how to get around this problem?
Paul
I installed Version 1.5.6 onto a 64-Bit Windows 7 Pro SP1 workstation with two drives.
The system's Windows Temp directory is D:\WINTEMP
Once I debugged my client/server configuration, I exported the connection to a .visz file.
I had a coworker install 1.5.6 onto his workstation (another 64-bit Windows 7 Pro SP1 workstation) and import the files that I exported.
When he tries connect to the OpenVPN server, a message appears, after about a minutes, saying it is disconnected.
The status windows shows....
Version 1.5.6 (1340) - Windows 7 Pro SP1 x64
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid if this is a Custom Gateway.
The log file shows ...
Jun 01 11:31:41 AM: State changed to Connecting
Jun 01 11:31:41 AM: Viscosity Windows 1.5.6 (1340)
Jun 01 11:31:41 AM: Running on Microsoft Windows 7 Professional
Jun 01 11:31:41 AM: Bringing up interface...
Jun 01 11:31:42 AM: Checking reachability status of connection...
Jun 01 11:31:43 AM: Connection is reachable. Starting connection attempt.
Jun 01 11:31:43 AM: Options error: Temporary directory (--tmp-dir) fails with 'D:\WINTEMP\': No such file or directory
Jun 01 11:31:43 AM: Options error: Please correct these errors.
Jun 01 11:31:43 AM: Use --help for more information.
The problem is this workstaton has no D: drive installed. It is a single drive system.
I checked the registry and found, under one of the viscosity entries, the D:\WINTEMP\ entry. I tried changing it to the actual Windows Temp directory and rebooted the workstation.
The same error came up and the Viscosity temp directory still pointed to the nonexistant D:\WINTEMP\ directory.
Does anyone know how to get around this problem?
Paul
Hi Paul,
Please edit your connection and go to the Advanced tab. Here you should see a command starting with 'tmp-dir'. Delete this line, save the connection and then try to connect again. You shouldn't need a tmp-dir defined at all, but for more information on the command, please see the OpenVPN manual - https://community.openvpn.net/openvpn/w ... n23ManPage
Regards,
Eric
Please edit your connection and go to the Advanced tab. Here you should see a command starting with 'tmp-dir'. Delete this line, save the connection and then try to connect again. You shouldn't need a tmp-dir defined at all, but for more information on the command, please see the OpenVPN manual - https://community.openvpn.net/openvpn/w ... n23ManPage
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi Eric,
I looked in the file and there was no tmp line.
It turns out that the users system TEMP and TMP files were set to D:\WINTEMP as well, and that directory didn't exist.!
Correcting those windows variables and rebooting the computer fixed the problem.
I'm going to test with a couple more Windows and Mac users, and if they can install w/o problems, I will move forward with purchasing licenses.
Great product. It will make my life so much easier than trying to deploy the OpenVPN clients!
Paul
I looked in the file and there was no tmp line.
It turns out that the users system TEMP and TMP files were set to D:\WINTEMP as well, and that directory didn't exist.!
Correcting those windows variables and rebooting the computer fixed the problem.
I'm going to test with a couple more Windows and Mac users, and if they can install w/o problems, I will move forward with purchasing licenses.
Great product. It will make my life so much easier than trying to deploy the OpenVPN clients!
Paul
Hi Paul,
Good to see you found the problem, that would have been our next suggestion to check the system variables.
Regards,
Eric
Good to see you found the problem, that would have been our next suggestion to check the system variables.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
5 posts
Page 1 of 1