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


keithdavis
2015-03-23T14:56:28Z
We just upgraded all of our machines to 7.6.3 and we have a new issue. We automatically connect to all VC servers (about 12) on launch of the client. This has never given any problems. With 7.6.3, some of these connections fail with the error message:

'Object reference not set to an instance of an object'

3 particular connections seem to be the only ones that fail:

  • DC10 (Server 2012 R2 x64 domain controller)
  • DC11 (Server 2012 R2 x64 domain controller)
  • localhost (all Windows 7 x64 Pro)


On the second attempt, this connection succeeds, most of the time. However, on at least one occasion, DC11 took 3 tries and on the second failure, failed with a completely different error message (long, screenshot attached).

Edit: Unable to attach images and don't have time to type out the entire message.

"Expected reply has not been received within time period...."
Sponsor
Forum information
keithdavis
2015-03-23T15:03:10Z
Upload attachments for the this forum is not working. I've used IE and Chrome. Upload succeeds, but then the files are not available.
Support
2015-03-23T16:09:10Z
Thanks, we are working on the attachment issue.

You are talking about local connection problems - not remote right?

Please send us the log_apiDATE.txt and log_serverDATE.txt to support@visualcron.com. You find the first file by right clicking on Tray client->Client->Log.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
keithdavis
2015-03-23T16:28:43Z
Originally Posted by: Support 

You are talking about local connection problems - not remote right?



No, local and remote. DC10 and DC11 are remote connections and the localhost is a local connection (local to the client). Sending logs now.

BartlebyX
2015-03-23T16:32:55Z
Originally Posted by: keithdavis 

We just upgraded all of our machines to 7.6.3 and we have a new issue. We automatically connect to all VC servers (about 12) on launch of the client. This has never given any problems. With 7.6.3, some of these connections fail with the error message:

'Object reference not set to an instance of an object'

3 particular connections seem to be the only ones that fail:


  • DC10 (Server 2012 R2 x64 domain controller)
  • DC11 (Server 2012 R2 x64 domain controller)
  • localhost (all Windows 7 x64 Pro)


On the second attempt, this connection succeeds, most of the time. However, on at least one occasion, DC11 took 3 tries and on the second failure, failed with a completely different error message (long, screenshot attached).

Edit: Unable to attach images and don't have time to type out the entire message.

"Expected reply has not been received within time period...."



You aren't the only one with this issue. We have three servers and all three are giving two of us this error since upgrading to 7.6.3. The third person isn't getting it, and I've had exactly one instance where I started the client and it didn't happen to at least two of them, but it all started immediately after hte upgrade.

Like you, if I try and connect manually after the errors come up, I can usually get them to connect on the second try, though sometimes it takes more.

The clients are all Windows 7 x64 pro. Two servers are running 2003 standard and one 'server' is running XP Pro (long story...moving it to 2012 soon).

The errors text is:

3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
Support
2015-03-23T16:43:39Z
Originally Posted by: BartlebyX 

Originally Posted by: keithdavis 

We just upgraded all of our machines to 7.6.3 and we have a new issue. We automatically connect to all VC servers (about 12) on launch of the client. This has never given any problems. With 7.6.3, some of these connections fail with the error message:

'Object reference not set to an instance of an object'

3 particular connections seem to be the only ones that fail:


  • DC10 (Server 2012 R2 x64 domain controller)
  • DC11 (Server 2012 R2 x64 domain controller)
  • localhost (all Windows 7 x64 Pro)


On the second attempt, this connection succeeds, most of the time. However, on at least one occasion, DC11 took 3 tries and on the second failure, failed with a completely different error message (long, screenshot attached).

Edit: Unable to attach images and don't have time to type out the entire message.

"Expected reply has not been received within time period...."



You aren't the only one with this issue. We have three servers and all three are giving two of us this error since upgrading to 7.6.3. The third person isn't getting it, and I've had exactly one instance where I started the client and it didn't happen to at least two of them, but it all started immediately after hte upgrade.

Like you, if I try and connect manually after the errors come up, I can usually get them to connect on the second try, though sometimes it takes more.

The clients are all Windows 7 x64 pro. Two servers are running 2003 standard and one 'server' is running XP Pro (long story...moving it to 2012 soon).

The errors text is:

3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267



The error is not really related. The above error is raised if the Exit code collection that you use for the specific Task does not contain the exit code that is produced.

Have you performed _all available_ Windows updates on Client and Server machine?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
BartlebyX
2015-03-23T16:52:10Z
Originally Posted by: Support 

Originally Posted by: BartlebyX 

Originally Posted by: keithdavis 

We just upgraded all of our machines to 7.6.3 and we have a new issue. We automatically connect to all VC servers (about 12) on launch of the client. This has never given any problems. With 7.6.3, some of these connections fail with the error message:

'Object reference not set to an instance of an object'

3 particular connections seem to be the only ones that fail:


  • DC10 (Server 2012 R2 x64 domain controller)
  • DC11 (Server 2012 R2 x64 domain controller)
  • localhost (all Windows 7 x64 Pro)


On the second attempt, this connection succeeds, most of the time. However, on at least one occasion, DC11 took 3 tries and on the second failure, failed with a completely different error message (long, screenshot attached).

Edit: Unable to attach images and don't have time to type out the entire message.

"Expected reply has not been received within time period...."



You aren't the only one with this issue. We have three servers and all three are giving two of us this error since upgrading to 7.6.3. The third person isn't getting it, and I've had exactly one instance where I started the client and it didn't happen to at least two of them, but it all started immediately after hte upgrade.

Like you, if I try and connect manually after the errors come up, I can usually get them to connect on the second try, though sometimes it takes more.

The clients are all Windows 7 x64 pro. Two servers are running 2003 standard and one 'server' is running XP Pro (long story...moving it to 2012 soon).

The errors text is:

3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267
3/23/2015 11:27:03 AM Err GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267



The error is not really related. The above error is raised if the Exit code collection that you use for the specific Task does not contain the exit code that is produced.

Have you performed _all available_ Windows updates on Client and Server machine?



Yes. I just checked my workstation and the servers are all up-to-date.

I found the actual login errors and they differ. I was simply quoting what our other admin gave me. I'll open a new thread for my login issue if that's what's appropriate.

Thank you!
Support
2015-03-23T16:55:17Z
Originally Posted by: BartlebyX 


I found the actual login errors and they differ. I was simply quoting what our other admin gave me. I'll open a new thread for my login issue if that's what's appropriate.

Thank you!



Please send the same files to support@visualcron.com and let us know if remote or local connection fails and what error you get in the Client when connecting.

Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
2015-03-27T08:09:51Z
Originally Posted by: keithdavis 

Upload attachments for the this forum is not working. I've used IE and Chrome. Upload succeeds, but then the files are not available.


It's working again.

Regards,
Erik
Uses Visualcron since 2006.
Support
2015-03-30T11:54:48Z
Originally Posted by: keithdavis 

We just upgraded all of our machines to 7.6.3 and we have a new issue. We automatically connect to all VC servers (about 12) on launch of the client. This has never given any problems. With 7.6.3, some of these connections fail with the error message:

'Object reference not set to an instance of an object'

3 particular connections seem to be the only ones that fail:


  • DC10 (Server 2012 R2 x64 domain controller)
  • DC11 (Server 2012 R2 x64 domain controller)
  • localhost (all Windows 7 x64 Pro)


On the second attempt, this connection succeeds, most of the time. However, on at least one occasion, DC11 took 3 tries and on the second failure, failed with a completely different error message (long, screenshot attached).

"Expected reply has not been received within time period...."



We believe we have fixed this issue in this build, please test it here:

http://www.visualcron.co....aspx?g=posts&t=4886 


Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
keithdavis
2015-03-30T13:33:38Z
Initial tests indicate that this problem is fixed.
Support
2015-03-31T11:51:54Z
Originally Posted by: keithdavis 

Initial tests indicate that this problem is fixed.



Thanks for the feedback!
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top