Symptoms:
The customer reported that they are using the .NET generator to consume imported web services.
The calling of one of the two web service was working fine, but they got an application error when they called another function in the same dll. If they always execute the same function, it works fine. If they execute the first web service and then the second web service, they get this error:
Log Name: Application
Source: Application Error
Date: 10/20/2015 16:34:13
Event ID. 1000
Task Category: (100)
Level: Error
Description:
Name of application errors: PlexRuntimeService.exe Version: 7.2.21.0, timestamp: 0x548f8387
Module name failed: clr.dll Version: 4.0.30319.296, timestamp: 0x50483916
Exception code: 0xc00000fd
Displacement error: 0x0000000000197cdb
Process id errors. 0xdc0
Start time of application errors: 0x01d10b43db7cb3e4
Path of application errors: C: \ Program Files (x86) \ CA \ Plex \ 7.2 \ Ob.NET \ Release \ PlexRuntimeService.exe
Path module with errors: C: \ Windows \ Microsoft.NET \ Framework64 \ v4.0.30319 \ clr.dll
Id Reporting. A1b0e7f8-7737-11e5-a2b4-005056ba622a
XML Event:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-10-20T14:34:13.000000000Z" />
<EventRecordID>1434</EventRecordID>
<Channel>Application</Channel>
<Computer>SRV-WSOBSY.finsa.loc</Computer>
<Security />
</System>
<EventData>
<Data>PlexRuntimeService.exe</Data>
<Data>7.2.21.0</Data>
<Data>548f8387</Data>
<Data>clr.dll</Data>
<Data>4.0.30319.296</Data>
<Data>50483916</Data>
<Data>c00000fd</Data>
<Data>0000000000197cdb</Data>
<Data>dc0</Data>
<Data>01d10b43db7cb3e4</Data>
<Data>C:\Program Files (x86)\CA\Plex\7.2\Ob.NET\Release\PlexRuntimeService.exe</Data>
<Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
<Data>a1b0e7f8-7737-11e5-a2b4-005056ba622a</Data>
</EventData>
</Event>
--
Environment:
Windows PC, .NET
Cause:
The details of the cause are unknown because this appears to be .NET framework (3rd party product) related error.
Resolution/Workaround:
Do a fresh install of .Net framework. With a fresh installation, the Web Service works as expected.