Loading Profile...
Vipre Ent Console 'Unable to connect to service...'
Installed VIPRE Enterprise + Console on a Win2ksp4 machine and 2 clients (1 of which is this same machine), all working fine. Then with NO changes to any machines, after 2 days, now cannot use Console! "Unable to connect to service...". Checked under 'services' and the Service is running. Also clients have not updated for 2 days now. This occurred after the first deep scans were done (scans completed normally). Should I reinstall? Just the Console or the whole thing? Note: Account/logon info was saved and has not changed since everything was working.
I’m frustrated.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thank you for contacting Sunbelt Software.
One of our support technicians will need to take a closer look at this issue. Please email support@sunbeltsoftware.com and we will have a support ticket created for you. Include your contact information, software version, and a brief description of the issue. One of our techs will contact you shortly.
We have a public Vipre Enterprise Discussion Forum which is closely monitored by much of our Vipre Enterprise team. It’s a place where valuable information is discussed between our customer’s and our staff. Topics like unforeseen environmental issues, workarounds, and fixes can all be found here. Customers who subscribe to this discussion forum will also be the first that are notified on product announcements in regards to software upgrades, threat definition updates, and features that will be added in future releases. Here is the link to subscribe to our forums. I hope to see you there.
http://www.sunbeltsoftware.com/Commun... -
Inappropriate?UPDATE: MS sent a sec update for dotnet; had to reboot after install, but then VIPRE Ent. service did not start automatically. Started service manually, and now everything is working again--connecting to console, agents updating. Will keep an eye on this, though.
I’m thankful
