Skip to content
Having trouble with profiles
Got a problem with Viscosity or need help? Ask here!
Any help will be appreciated.. I installed viscosity on an admin account for our roaming profiles and push the config files on the server on the appdata but I still get this error
Jan 17 10:20:13: State changed to Disconnected
Jan 17 10:20:15: State changed to Connecting
Jan 17 10:20:15: Viscosity 1.4.6 (1212)
Jan 17 10:20:15: Running on Microsoft Windows 7 Professional
Jan 17 10:20:15: Bringing up interface...
Jan 17 10:20:15: Checking reachability status of connection...
Jan 17 10:20:15: Connection is reachable. Starting connection attempt.
Jan 17 10:20:15: Configuration not found, Aborting
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.
Jan 17 10:20:25: State changed to Disconnected
Jan 17 10:20:13: State changed to Disconnected
Jan 17 10:20:15: State changed to Connecting
Jan 17 10:20:15: Viscosity 1.4.6 (1212)
Jan 17 10:20:15: Running on Microsoft Windows 7 Professional
Jan 17 10:20:15: Bringing up interface...
Jan 17 10:20:15: Checking reachability status of connection...
Jan 17 10:20:15: Connection is reachable. Starting connection attempt.
Jan 17 10:20:15: Configuration not found, Aborting
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.
Jan 17 10:20:25: State changed to Disconnected
Hi jcg,
We've seen a problem similar to this before when non-standard %appdata% folders are used. The following needs to be true for everything to work as expected:
The %appdata% system variable needs to correctly point to where your roaming profiles folder is for each user (by default C:\Users\user\AppData\Roaming).
The SYSTEM user needs to have access to view these appdata folders in order to be able to read the config files. We have seen GPOs that lock the SYSTEM user out from access to the file system completely in the past. To test if this is the issue, change the user that runs ViscosityService.exe to an administrative user and see if the problem still occurs. If you're unsure on how to do this, please let us know and we can walk you through it.
Regards,
Eric
We've seen a problem similar to this before when non-standard %appdata% folders are used. The following needs to be true for everything to work as expected:
The %appdata% system variable needs to correctly point to where your roaming profiles folder is for each user (by default C:\Users\user\AppData\Roaming).
The SYSTEM user needs to have access to view these appdata folders in order to be able to read the config files. We have seen GPOs that lock the SYSTEM user out from access to the file system completely in the past. To test if this is the issue, change the user that runs ViscosityService.exe to an administrative user and see if the problem still occurs. If you're unsure on how to do this, please let us know and we can walk you through it.
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 jcg,
Please try running the service as an Admin account rather than the SYSTEM user. To do this:
Go to start, type in services and run the Services.msc snap-in.
Locate Viscosity Service, right click it and go to Properties
Click Stop, then go to the Log On tab
Change the dialog to "This account" and enter the login information for a Local Administrator account. A Domain Admin account may work, but you will need to experiment with this as it will differ depending on your AD setup.
Click Apply, go back to the General tab and start the service
Attempt to connect again.
Regards,
Eric
Please try running the service as an Admin account rather than the SYSTEM user. To do this:
Go to start, type in services and run the Services.msc snap-in.
Locate Viscosity Service, right click it and go to Properties
Click Stop, then go to the Log On tab
Change the dialog to "This account" and enter the login information for a Local Administrator account. A Domain Admin account may work, but you will need to experiment with this as it will differ depending on your AD setup.
Click Apply, go back to the General tab and start the service
Attempt to connect again.
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
4 posts
Page 1 of 1