7 Replies Latest reply on Jun 10, 2015 3:57 PM by aseck

    PI SDK IIS Crash


      We are using PI SDK in an IIS Web Application. The application was working fine on PI SDK 1.3.8.


      We upgraded it to and now I see a lot of errors as below


      Faulting application w3wp.exe, version 7.0.6002.23330, time stamp 0x5304757e, faulting module ole32.dll, version 6.0.6002.18277, time stamp 0x4c28d53e, exception code 0xc0000005, fault offset 0x00047336, process id 0x1774, application start time 0x01d0a2450d9d4cd6.


      This is crashing the worker process and bringing up the login dialog to the user.


      Can you please suggest a fix for this?

        • Re: PI SDK IIS Crash

          PI SDK Error


          Faulting application w3wp.exe, version 7.0.6002.23330, time stamp 0x5304757e, faulting module pisdk.dll, version, time stamp 0x53ee3ffa, exception code 0xc0000005, fault offset 0x00145953, process id 0x11b0, application start time 0x01d0a24186342038.

          • Re: PI SDK IIS Crash

            This is the dump from DebugDiag


            Report for W3WP__~2.DMP

            Type of Analysis Performed  Crash Analysis
            Machine Name  XXXXXXXXXXXX
            Operating System  Windows Server 2008 Service Pack 2
            Number Of Processors  2
            Process ID  3244
            Process Image  C:\Windows\SysWOW64\inetsrv\w3wp.exe
            System Up-Time  17:24:24
            Process Up-Time  00:02:10


            Thread 41 - System ID 292

            Entry point  ole32!CoSetState+96c
            Create time  6/9/2015 2:42:53 AM
            Time spent in user mode  0 Days 0:0:5.984
            Time spent in kernel mode  0 Days 0:0:0.843




            Full Call Stack



            Function    Arg 1    Arg 2    Arg 3    Arg 4  Source
            pisdk!CPISDK::get_Servers+1b3    123dfb98    12b1fc00    00000202    00000002 
            rpcrt4!NdrServerInitialize+3eb    731857a0    117ff120    00000002    ac2aad59 
            rpcrt4!NdrStubCall2+28b    1153a340    111b16e0    017178e8    117ff370 
            rpcrt4!NdrProxyErrorHandler+3c    1153a340    017178e8    111b16e0    111b77a8 
            oleaut32!LoadRegTypeLib+95f    1153a340    017178e8    111b16e0    ac2aaca3 
            ole32!WdtpInterfacePointer_UserUnmarshal+1e09    017178e8    020962a4    111b77a8    735f023c 
            ole32!WdtpInterfacePointer_UserUnmarshal+1f9d    017178e8    111c3e40    129bda20    111b16e0 
            ole32!CoRevokeClassObject+b145    111b16e0    00000000    129bda20    01f6a040 
            ole32!CoRevokeClassObject+b056    017178e8    00000001    129bda20    111b16e0 
            ole32!DcomChannelSetHResult+7c9    017178e8    00000001    129bda20    111b16e0 
            ole32!WdtpInterfacePointer_UserUnmarshal+1ec5    d0908070    111b16e0    129bda20    123dfb98 
            ole32!WdtpInterfacePointer_UserUnmarshal+1cdf    01717890    01f6a040    00000000    01717890 
            ole32!WdtpInterfacePointer_UserUnmarshal+2371    01717890    00000400    02082648    117ff6f8 
            ole32!DcomChannelSetHResult+5a1    01717890    00000000    77006b6f    00000000 
            ole32!DcomChannelSetHResult+560    00f50152    00000400    0000babe    01717894 
            user32!GetWindowLongW+250    77006b6f    00f50152    00000400    0000babe 
            user32!GetWindowLongW+3c7    00000000    77006b6f    00f50152    00000400 
            user32!GetWindowLongW+4f2    77006b6f    00000000    117ff844    76ff8030 
            user32!DispatchMessageW+f    117ff828    00000000    770e1bb0    00000000 
            ole32!CoFreeAllLibraries+22ff    00007530    75ba11e1    111b0808    00000b64 
            ole32!CoFreeAllLibraries+2410    117ff884    7700ebd6    770e1bb0    00000000 
            ole32!CoFreeAllLibraries+2352    770e1bb0    00000000    111b0808    111b0808 
            ole32!CreateBindCtx+b08    00000000    00000000    117ff8a0    75c1f804 
            ole32!CoSetState+982    111b0808    117ff8e0    777bd7bd    111b0808 
            kernel32!BaseThreadInitThunk+e    111b0808    6547d690    00000000    00000000 
            ntdll!RtlCreateUserProcess+8c    76ff57e9    111b0808    ffffffff    777de25b 
            ntdll!RtlCreateProcessParameters+4e    76ff57e9    111b0808    00000000    00000000 






            Exception Information

            PISDK!CPISDK::GET_SERVERS+1B3In W3WP__~2.DMP the assembly instruction at pisdk!CPISDK::get_Servers+1b3 in D:\Program Files (x86)\PIPC\pisdk\pisdk.dll from OSIsoft, LLC. has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 41




            Module Information

            Image Name:D:\Program Files (x86)\PIPC\pisdk\pisdk.dll  Symbol Type: PDB
            Base address:0x00905a4d  Time Stamp: Fri Aug 15 10:14:34 2014
            Checksum:0x0205c1e2  Comments: Build 484, Friday, August 15, 2014
            COM DLL:True  Company Name: OSIsoft, LLC.
            ISAPIExtension:False  File Description: PI SDK 32-bit module
            ISAPIFilter:False  File Version:
            Managed DLL:False  Internal Name: PISDK
            VB DLL:False  Legal Copyright: (c) 1998-2014 OSIsoft, LLC. All Rights Reserved.
            Loaded Image Name: pisdk.dll  Legal Trademarks: PI System and PI SDK are trademarks of OSIsoft, LLC.
            Mapped Image Name:   Original filename: PISDK.dll
            Module name: pisdk  Private Build:
            Single Threaded: False  Product Name: PI Software Development Kit
            Module Size: 8.09 MBytes  Product Version:
            Symbol File Name: c:\windows\symbols\dll\PISDK.pdb  Special Build: &
              • Re: PI SDK IIS Crash

                Hello Mahesh,


                From what I can see, you have a Tech Support case opened on this issue, and this is probably the best way to proceed, given the level of troubleshooting needed at first. As suggested by my coworker Maryam, you will need to provide a full crash dump (not just the trace above) for analysis.

                You maybe running into a known issue found in later versions of the PI SDK (this one, for example), but we will need to take a look at the full crash dump to confirm. It would also be good to know how often the issue occurs.


                Once we confirm whether or not you are running into the aforementioned issue, we would need to know what your application does exactly, and try to identify where it crashes. However, like I said, the first step is to work with Tech Support to identify the exact source of the crash.

                  • Re: PI SDK IIS Crash

                    Hi Alassane,


                    Thank you for getting back!


                    We downgraded the SDK to 1.4.0 and that resolved the issue.


                    Yes, the PI SDK 1.4.4 and 1.4.2 both seem to have the issue.




                      • Re: PI SDK IIS Crash

                        Hi Mahesh,


                        While I am glad that you are not running into the issue anymore, it is unfortunate that you had to downgrade PI SDK. I encourage you to continue working with our Tech Support to get to the bottom of the issue.


                        On another train of thought, PI SDK is headed towards deprecation in the upcoming years (See Ray's blog post here). Therefore we strongly encourage you to consider transitioning your application to use PI AF SDK or one of our other data access technologies.




                          • Re: PI SDK IIS Crash

                            H Alassane,


                            This application was built on PI SDK ( about 5 years back) and is a very critical application used by our Operators and The Traders for Situational Awareness.


                            For all new development we are using AF SDK and don't use PI SDK. That's the reason we don't want to spend any time fixing the old application to work with the PI SDK 1.4.4 or 1.4.2.


                            We are planning to eventually migrate this application to use AF SDK.




                              • Re: PI SDK IIS Crash



                                That is good to hear!


                                Unless you have further questions, may I ask that you close the loop by marking the question as 'Answered'? You can do so by marking the answered deemed as the most helpful as 'Correct Answer'