Symptom

During a Login VSI test an error pop-up can show which originates from the "login vsi management console.exe" process. It will usually occur during the session ramp-up phase of the test. The message might look like this: 

Cause

The VSIshare host's IO or networking likely is overloaded

Resolution

Potential resolutions are:

1. Restart the VSIshare host and re-run a test
2. If the issue persists then monitor the IO and networking usages on the VSIshare host
   1. Increase VSIshare host resources if need be. In this case, if spinning local storage media is used, its recommended using, or migrating the local storage to, a flash hard drive or RAM disk
   2. In some cases adding more Login VSI web and content shares can lessen the VSIshare host load, especially during tests of 1000 or more test sessions.
      • Refer to instructions to add more shares here

3. Check time differences between targets and the VSIshare host. If there is a large deviation this error can occur

4.  Reinstalling .net 3.5 can potentially resolve the issue

5.  Try running the "Login VSI Management Console.exe" as an admin user

Note: closing the "Login VSI Management Console.exe" UI and closing the error message box during a test will not interrupt the testing, though it will not resolve the aforementioned potential issues.

Properties

Applies to

Login VSI 4.x

Below is the potential stack trace of the error's occurrence to assist with this article's search-ability:

Object reference not set to an instance of an object.
at Login.VSI_Management_Suite.Forms.SubForms.subDashboardActive.GetLogonTimes()
at Login.VSI_Management_Suite.Forms.SubForms.subDashboardActive.CounterThread()
at System.Threading.ExecutionContext.RunInternal(ExecutionContextexecutionContext, ContextCallback callback, Object state, BooleanpreserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContextexecutionContext, ContextCallback callback, Object state, BooleanpreserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContextexecutionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()