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
Ask a question
The Unit Testing Company
Development Resources
Knowledge Base
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.

Related questions

AutoRunner causes Win32 exception - Access is denied

0 votes
Hi,

I have TypeMock Isolator 7.0.7 installed with AutoRunner and TestLint (TestLint is disabled in ExtensionManager). When I enable AutoRunner and it's running in the background, I receive the error below displayed in the Output window.

I am running Win7 x64 SP1 with VisualStudio 2010 SP1 (run as Administrator). 
START: Scan
END  : 00:00:00.2492247
START: Analyzing test projects
END  : 00:00:01.2671211
START: Loading solution tests information
END  : 00:00:00.0169343
START: UpdateAssembliesWhiteList
END  : 00:00:00.0503583
START: GetAllTests
END  : 00:00:00.0000150
START: Executing tests
Failed killing daemon: System.ComponentModel.Win32Exception (0x80004005): Access is denied
   at System.Diagnostics.Process.Kill()
   at Typemock.Common.Core.DaemonNUnitRunner.KillDaemon(Process process)
Failed killing daemon: System.ComponentModel.Win32Exception (0x80004005): Access is denied
   at System.Diagnostics.Process.Kill()
   at Typemock.Common.Core.DaemonNUnitRunner.KillDaemon(Process process)
Test run failed more than 1 times - aborting
Test run failed more than 1 times - aborting
System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
   at System.ServiceModel.Channels.PipeConnection.FinishSyncRead(Boolean traceExceptionsAsErrors)
   at System.ServiceModel.Channels.PipeConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.ServiceModel.Channels.PipeConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
   at System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
   at System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout)
   at System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.Receive(TimeSpan timeout)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Typemock.Common.Core.ITestRunnerService.RunTests(List`1 assemblies, List`1 testNames, String sessionID, Dictionary`2 testsOptions)
   at Typemock.Common.Core.TestRunnerServiceSynched.RunTests(List`1 assemblies, List`1 testNames, String sessionID, Dictionary`2 testsOptions)
   at Typemock.Common.Core.DaemonNUnitRunner.PerformRunTests(List`1 testsAssemblies, IEnumerable`1 testNames, Guid sessionGuid, Dictionary`2 testOptions)
   at Typemock.Common.Core.DaemonNUnitRunner.<>c__DisplayClass5.<TryRunTests>b__0()
END  : 00:01:14.3289278
START: Loading test results
END  : 00:00:00.0060379
Test run results - 
unexpected error when trying to run test: VCI.Enterprise.AccountProcessing.Tests.SilverPopHelperTest.ShouldSendEmail
unexpected error when trying to run test: VCI.Enterprise.AccountProcessing.Tests.SilverPopRepositoryWrapperTest.SendTransactEmail_Should_Not_Throw_Exception_When_UpdateType_Is_Not_Correct
unexpected error when trying to run test: VCI.Enterprise.AccountProcessing.Tests.VciCreateAccountPayoffQuoteModuleTest.CreateMessageRequestForPayoffQuote
unexpected error when trying to run test: VCI.Enterprise.AccountProcessing.Tests.VciCreateAccountPayoffQuoteModuleTest.CheckIfPayoffCreateRequestIsValid_Test
...
...
asked by dblack
Report User
 (8.4k points)

62 Answers

0 votes
Hi Nofar,

Please find the attached logs as required. Please let me know if required any other information on same.

Thanks & Regards
Teena Sharma

Logs.zip
answered by teenasharma
Report User
 (1.4k points)
0 votes
Hi Teena,

System.Configuration.ConfigurationErrorsException: Only one <configSections> element allowed per config file and if present must be the first child of the root <configuration> element


This means that when you copy your app.config content into Isolator's app.config you should paste it inside <configuration> </configuration> tags. There can be only one set of these tags per app.config file (this is the root element). 


<configuration> 
        typemock configurations...
</configuration>


<configuration> 
         your configurations...
</configuration>


<configuration> 
         typemock configurations...

         your configurations...
</configuration>


Please make sure that you follow this example.
If this doesn't help please send me the merged app.config file.
answered by alex
Report User
 (17k points)
0 votes
Hi,

The app.config issue should be fixed in the next version (7.1.7).

Meanwhile, please Install this patch and let us know if it helps.
answered by alex
Report User
 (17k points)
0 votes
Hi Alex,

The shared link is not working for me https://www.typemock.com/files/patches/T ... gPatch.msi
Its saying file not found. Please share the updated link so that i can try it.

Thanks & Regards
Teena Sharma
answered by teenasharma
Report User
 (1.4k points)
0 votes
Hi,

Thank you for the correction. Fixed it.
answered by alex
Report User
 (17k points)
0 votes
Hi Alex,

We are still facing the issue in reading the connection string from the project's app.config with auto-runner. But when we run the unit tests after disable auto-runner feature we are able to read the connection string as it was before.

We noticed the inporovement in the shared patch 7.1.6 is that now when we build the project, it does not gives pop up error and also loads the autorunner symbols with saying all unit tests fails.

Please use the previously shared demo project to see the results.

Thanks & Regards
Teena Sharma
answered by teenasharma
Report User
 (1.4k points)
0 votes
Hi Teena,

I apologize again, this is the right link.

Looking forward for your feedback.
answered by NofarC
Report User
 (4k points)
0 votes
Hi Alex,
This is Nilesh Singh. I will be working on this TypeMock issue instead of Teena Sharma.
I have installed the latest patch shared by you.
We are having two scenarios:
1. While running the Type Case manually “using debug test case icon”. It is working fine as expected. (When we run the unit tests after disable auto-runner feature)
2. Once I enable “Type Mock Smart Runner” feature and try to build the solution at that time “Auto runner feature” start executing my test cases and it start giving the error (failed test cases).
I had debug the issue and found that it is unable to find the connection string from the app.config file. But when I had hard code the value in my code it starts giving another error.
Exception: “The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.”
I have attached three files (screen shot).
1. ManualDebugTypeMock.png – Type mock working fine.
2. AutoRunnerDebugUsingTypeMock.png – Reading data from app.config file (Not working “giving object ref not set exception”).
3. AutoRunnerDebugUsingTypeMock_AfterHardCode.png – After hard code the values. (Again not working – “The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.”)
Please do let me know if you need more information.

Regards,
Nilesh Singh
j.nilesh.singh@gmail.com

AutoRunnerDebugUsingTypeMock_AfterHardCode.png

AutoRunnerDebugUsingTypeMock.png

ManualDebugTypeMock.png
answered by Nilesh Singh
Report User
 (580 points)
0 votes
Hi Alex,
This is Nilesh Singh. I will be working on this TypeMock issue instead of Teena Sharma.
I have installed the latest patch shared by you.
We are having two scenarios:
1. While running the Type Case manually “using debug test case icon”. It is working fine as expected. (When we run the unit tests after disable auto-runner feature)
2. Once I enable “Type Mock Smart Runner” feature and try to build the solution at that time “Auto runner feature” start executing my test cases and it start giving the error (failed test cases).
I had debug the issue and found that it is unable to find the connection string from the app.config file. But when I had hard code the value in my code it starts giving another error.
Exception: “The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.”
I have attached the three screen shot.
1. ManualDebugTypeMock.png – Type mock working fine.
2. AutoRunnerDebugUsingTypeMock.png – Reading data from app.config file (Not working “giving object ref not set exception”).
3. AutoRunnerDebugUsingTypeMock_AfterHardCode.png – After hard code the values. (Again not working – “The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.”)
Please do let me know if you need more information.

Regards,
Nilesh Singh
j.nilesh.singh@gmail.com
answered by Nilesh Singh
Report User
 (580 points)
0 votes
Hi Alex,

Any update on this??

Regards,
Nilesh Singh
answered by Nilesh Singh
Report User
 (580 points)
Page:
...

Products

Help

Company

Community

Contact

Typemock Store (US toll FREE 866–895–4680). Copyright © 2006 Typemock Inc. All rights reserved. Terms of Use.