Hi Henrik

I have installed the lates version of VC (7.6.0) over the top of V7.07 (using local Admin). However, now the VC Service will not start.

Installed on Windows 2008 R2 Server, and the windows event log is giving me the following Error:
Faulting application name: VisualCronService.exe, version: 7.6.0.31029, time stamp: 0x54e2175c
Faulting module name: clr.dll, version: 4.0.30319.1008, time stamp: 0x517a18ff
Exception code: 0xc00000fd
Fault offset: 0x000000000001f823
Faulting process id: 0x13d8
Faulting application start time: 0x01d04b688c9c9057
Faulting application path: C:\Program Files (x86)\VisualCron\VisualCronService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: cb031528-b75b-11e4-9484-005056b9000b


Ran a wmic query to test the versions of .NET installed and it returned the following:

C:\Users\paynxxxx>wmic /namespace:\\root\cimv2 path win32_product where "name like '%%.NET%%'" get version
Version
4.0.30319
4.0.30319


I have attached the Install log although it doesn't give much information.

Any ideas?

Thanks

Andy

Please send log_serverDATE.txt along with an export of your settings to support@visualcron.com

---

We have the same issue

We have the same issue

The reason behind the failure of first customer is that he had installed VC on a network drive or changed the settings folder to a network drive which VC could not access. Please send us your files.

---

It looks like with us it doesn't like the admin password although we haven't changed it. Is there a way to reset it?

Sorry with us the service starts but the client will not connect.
It looks like it doesn't like the admin password although we haven't changed it. Is there a way to reset it?

Sorry with us the service starts but the client will not connect.
It looks like it doesn't like the admin password although we haven't changed it. Is there a way to reset it?

Stop the service. Delete users.xml and usergroups.xml. Start service and logon with admin and a blank password.

---

Unfortunately still not working.

The server logs show this

18/02/2015 13:21:42 Debug Assembly loaded: System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
18/02/2015 13:21:42 Debug Starting up
18/02/2015 13:21:42 Debug Loading settings
18/02/2015 13:21:42 Debug Assembly loaded: System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
18/02/2015 13:21:42 Debug Assembly loaded: Microsoft.GeneratedCode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
18/02/2015 13:21:43 Debug Assembly loaded: ZetaLongPaths, Version=1.0.0.4, Culture=neutral, PublicKeyToken=b764f59068f31f38

The client shows this

18/02/2015 13:21:56 Could not connect to server. Error: There was no endpoint listening at net.pipe://localhost/ that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
18/02/2015 13:22:07 Connecting to VisualCron Server
18/02/2015 13:22:07 Could not connect to server. Error: Expected reply has not been received within time period.
18/02/2015 13:22:26 Connecting to VisualCron Server
18/02/2015 13:22:37 Connecting to VisualCron Server
18/02/2015 13:22:37 Could not connect to server. Error: Expected reply has not been received within time period.
18/02/2015 13:22:56 Connecting to VisualCron Server
18/02/2015 13:22:56 Could not connect to server. Error: Expected reply has not been received within time period.
18/02/2015 13:23:07 Connecting to VisualCron Server
18/02/2015 13:23:07 Could not connect to server. Error: Expected reply has not been received within time period.

Lets continue in the chat instead. Might be faster to solve there.

---

Hi Guys,

I have exactly the same issue here. Basically i did a VM clone using VMware and after that i get an error message when starting VS Client (Connection Failed to localhost). The problem is impacting the initial VM and the Clone.



Here are the Windows Event Viewer details:

Faulting application name: VisualCronService.exe, version: 8.1.2.36471, time stamp: 0x577d58e0
Faulting module name: clr.dll, version: 4.6.81.0, time stamp: 0x5584e818
Exception code: 0xc00000fd
Fault offset: 0x000000000005f007
Faulting process id: 0x884
Faulting application start time: 0x01d1e8d2870d8afc
Faulting application path: C:\Program Files (x86)\VisualCron\VisualCronService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: c53d36f3-54c5-11e6-89f7-0050568b9a70
Faulting package full name:
Faulting package-relative application ID:


--> VS Server Logs:

28-07-16 00:00:00 Err Error retrieving unique information: System.Management.ManagementException: Invalid class
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementBaseObject.get_Properties()
at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.KHJLGIADIIFEHGAGCJLOAPGNKDFPKOMIBFME.BKNLBOFLGBOKOMHOFOGIHMBMCJPJKFHDJAAO(String ) in C:\sourcefiles\code\VisualCronService\apiActivation.vb:line 327


--> TrayClient Logs:

28-07-16 11:34:03 Tray Client is starting up
28-07-16 11:34:03 Loading exit codes
28-07-16 11:34:04 Loaded language files.
28-07-16 11:34:04 InitServiceController
28-07-16 11:34:04 Running as user name: Administrator, user domain name: "Machine Name", interactive: True
28-07-16 11:34:04 Connecting to VisualCron Server
28-07-16 11:34:05 Could not connect to server. Error: There was no endpoint listening at net.pipe://localhost/VisualCron/ that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.


Could you please help me ?

Thank you,
J.

1. make sure that Windows Management Instrumentation service is running before starting VisualCron
2. open Windows Management Instrumentation in Computer Management and check that /root/ cimv2 is set and that you have no errors opening it

---

Hi Henrik,

Indeed it was an issue related to a missing parameter in the WMI. I’ve applied the following procedure to fix this.

https://blogs.technet.mi...rs-or-invalid-wmi-class/ 

Many thanks !!

Jonathan