chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes

All of a sudden, my Typemock is not integrating properly with Visual Studio 2017. When I try to *run* or *debug* a test, either from the context menu or the test runner, I get the following error:

Message: TypeMock.TypeMockException : 

*** Typemock Isolator is currently disabled. Enable using the following:

 * Within Visual Studio: 

 * Use Typemock Smart Runner  

 * For other runners, Choose Typemock Menu and click "Integrate with Other Runners" 

 * To run Typemock Isolator as part of an automated process you can:

    - run tests via TMockRunner.exe command line tool

    - use 'TypeMockStart' tasks for MSBuild or NAnt 

For more information consult the documentation (see 'Running Unit Tests in an Automated Build')

I am running

  • Visual Studio version: 15.9.14
  • Typemock version: 8.6.0.10

It may be relevant that I recently installed dotTrace (and subsequently uninstalled it).

asked by davidpoxon (600 points)

1 Answer

0 votes

Hi David,

I would like you to check 2 things:

1) have you activated your license? if not please activate it via our extension tab in Visual Studio or via our Isolator Configurator.

2) check if the "Integrate with other runners" box is checked, you can check it from our Isolator Configurator or via the extension tab in Visual Studio.

Cheers,

Alon Sapozhnikov.

Support Specialist. 

answered by Alon_TypeMock (10.6k points)
The license is activated and \'Integrate with other runners\' is checked.
Hi, any further thoughts on this? This issue is blocking my development process.

Hi David,

I tried to reproduce the issue, with no luck.

I even installed doTrace and uninstalled it and everything works for me.

Can you please try and uninstall Typemock Isolator, run devenv /setup command in the Developer Command Prompt for VS 17 and then install Isolator again.

If the issue remains, please send us a sample project so we would try and reproduce the issue.

Cheers,

Alon Sapozhnikov

Support Speciallist.

Where should I sent the sample project?

Hi David,

You can open a ticket in our ticket portal(under the Support tab in the site there's Premium Support) and there you can open a new ticket.

Please add all the relevant information including the original question and the sample project to reproduce.

Cheers,

Alon Sapozhnikov

Support Speciallist

I put together a sample program, but realised it probably wouldn't help as it would like work for you.

However, I did enable the SmartRunner and tried to run a test and received this exception that I thought could be of help:

 Unhandled Exception: 

> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

>    at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)

>    at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)

>    at System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(IMessage msg)

>    at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)

>    at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args)

>    at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)

>    at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)

>    at System.Runtime.Remoting.Channels.CrossAppDomainSink.SyncProcessMessage(IMessage reqMsg)

>    at System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(IMessageSink ms, IMessage reqMsg, ArrayWithSize proxySinks, Thread currentThread, Context currentContext, Boolean bSkippingContextChain)

>    at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMessage reqMcmMsg, Boolean useDispatchMessage, Int32 callType)

>    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

>    at Typemock.Common.Core.CoverageInitializerPorxy.InitSession(IEnumerable`1 assemblies, Boolean isBlacklist)

>    at Typemock.Common.TestsRunner.Lib.AssemblyTestsExecuter.ExecuteAssemblyTests(String sessionID, String assembly, CancelState cancelState, TestsSessions tests, AppDomain appDomain, String[] coveredAssemblies)

>    at Typemock.Common.TestsRunner.Lib.TestRunnerService.ExecuteAssemblyTests(String sessionID, AppDomainBuilder appDomainBuilder, String assembly, CancelState cancelState, TestsSessions tests, String[] coveredAssemblies)

>    at Typemock.Common.TestsRunner.Lib.TestRunnerService.RunTestInAppdomain(IEnumerable`1 testsAssemblyLocation, List`1 testNames, String sessionID, Dictionary`2 testsOptions, List`1 path2TestSettings, String solutionName, String[] coveredAssemblies, IEnumerable`1 dependencyFiles)

>    at Typemock.Common.TestsRunner.Lib.TestRunnerService.RunTests(IEnumerable`1 assemblies, List`1 testNames, String sessionID, Dictionary`2 testsOptions, List`1 path2TestSettings, String solutionName, String[] coveredAssemblies, LoggerOptions logOptions, IEnumerable`1 dependencyFiles)

>    at SyncInvokeRunTests(Object , Object[] , Object[] )

>    at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

>    at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

>    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

>    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)

>    at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

>    at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)

>    at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)

>    at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)

>    at System.ServiceModel.Dispatcher.ChannelHandler.OnAsyncReceiveComplete(IAsyncResult result)

>    at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)

>    at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

>    at System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)

>    at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)

>    at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

>    at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)

>    at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)

>    at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

>    at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)

>    at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

>    at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

Hi David,

It will be very helpful if you will open a ticket in our ticket portal.

Include all the relevant info, you can also send the sample program you were talking about.

Additionally, please send us the logs of the run(enable the logs in the configuration).

Cheers,

Alon Sapozhnikov

Support Specialist

...