Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Guest
2018-09-21T20:04:46Z
Hello Everyone,
Issue:
Visual cron service is not starting in services.msc
Even if we started manually, just after refreshing the services window, that is getting stopped.


Description:
We have a new server and at first, Visual cron is installed in D drive.. At this point, it was working fine.
But, due to requirement, the drive was named to G from D.
Then again it was made as D and then uninstalled Visual cron.
Finally, drive was named to G and then installed VisualCron 8.2.7 selecting that folder in G drive.

Note: We tried the same with latest version 8.3.6 also and same issue was there

Now we are unable to open visual cron.
For first time after login.. Error: cannot open visualcron service on computer is coming(The error is probably due to user permissions - was mentioned in same window)
Getting connection failed to localhost error even after waiting for more minutes..

In services.msc, when we checked.. Visual cron is showing as stopped . When we started this, again it is getting stopped automatically even after pressing refresh in services window.

We checked and can find the following error
9/21/2018 2:29:40 AM Err Error loading settings: System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Nielsen\VisualCron\settings\settings_server.xml'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)
at System.IO.StreamReader..ctor(String path, Encoding encoding)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.DNIKJOPGFECCBCCDJLGCJELOJOLMFDAAMPOL.AFPAJLJGMPPLGGPABDOPLIPDADFDPIMBMKKE(String , Boolean , Boolean ) in C:\sourcefiles\code\VisualCronService\Settings\apiSettings.vb:line 373


Got following in log_trayclient file
8/23/2018 5:21:24 AM 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.

Following error in log_server
Error: System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Nielsen....*

In server_startup log, we can see that for settings, VisualCron is still referring to D drive even after relabelling that to G drive.. D:\Nielsen\VisualCron\settings
We have checked and the drive relabel process was entirely correct and looks similar as in other working servers.


We have tried with 8.3.6 version of VC also and same problem exists


Someone help us to get visualcron service started and running.
Sponsor
Forum information
Guest
  •  Gavin
  • No customer Topic Starter
2018-09-25T08:27:12Z
Hi, can anyone from support provide some guidance on this issue?
Support
2018-09-25T09:23:39Z
Hi,

there are two places to check for. First you need to ensure that the VisualCron service is stopped.

1. look at server_settings.xml and update any paths there
2. edit the registry and update the path to the right server_settings.xml. You find it in Local machine->Software->V-C->ServerSettingsFolder

Start the VisualCron service.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guest
2018-09-25T16:45:59Z
Thanks for your help Gavin and support.

Editing the registry solved the issue
Scroll to Top