w3svc service crashes - something to do with Emfgen.dll

***********************
Starting new log output
IISState version 3.3.1

Sat Feb 18 11:50:57 2006

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3032

Note: Thread times are formatted as HH:MM:SS.ms

***********************


IIS has crashed...
Beginning Analysis
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\crystal\Emfgen.dll -
DLL (!FunctionName) that failed: Emfgen




Thread ID: 30
System Thread ID: 944
Kernel Time: 0:0:0.875
User Time: 0:0:10.843
Thread Type: Other
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be
wrong.
00 1050eeb0 5020726f Emfgen+0x146d
01 66207365 00000000 0x5020726f
Closing open log file C:\iisstate\output\IISState-3032.log
Opened log file 'C:\iisstate\output\IISState-3032.log'

***********************
Starting new log output
IISState version 3.3.1

Sat Feb 18 11:51:49 2006

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3032

Note: Thread times are formatted as HH:MM:SS.ms

***********************

RE: w3svc service crashes - something to do with Emfgen.dll

Emfgen.dll is part of Crystal Reports. You need to follow up with the
vendor to find out why this file is causing IIS to crash.

Thank you,

Jackie Jaynes [MSFT]
Microsoft IIS

Please do not send email directly to this alias. This
is our online account name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

RE: w3svc service crashes - something to do with Emfgen.dll

I am having the similiar problem. Did you find the solution?

Thanks.

"Tanveer Ansari" wrote:

> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Sat Feb 18 11:50:57 2006
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3032
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
> IIS has crashed...
> Beginning Analysis
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> C:\WINDOWS\crystal\Emfgen.dll -
> DLL (!FunctionName) that failed: Emfgen
>
>
>
>
> Thread ID: 30
> System Thread ID: 944
> Kernel Time: 0:0:0.875
> User Time: 0:0:10.843
> Thread Type: Other
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 00 1050eeb0 5020726f Emfgen+0x146d
> 01 66207365 00000000 0x5020726f
> Closing open log file C:\iisstate\output\IISState-3032.log
> Opened log file 'C:\iisstate\output\IISState-3032.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Sat Feb 18 11:51:49 2006
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3032
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************

Re: w3svc service crashes - something to do with Emfgen.dll

Have you confirmed that emfgen.dll is causing the crash?


Pat

"Kelly Bills" wrote in message
news:B3F015E7-83F9-4166-AB94-0138CD4C4892@microsoft.com...
>I am having the similiar problem. Did you find the solution?
>
> Thanks.
>
> "Tanveer Ansari" wrote:
>
>> ***********************
>> Starting new log output
>> IISState version 3.3.1
>>
>> Sat Feb 18 11:50:57 2006
>>
>> OS = Windows 2003 Server
>> Executable: w3wp.exe
>> PID = 3032
>>
>> Note: Thread times are formatted as HH:MM:SS.ms
>>
>> ***********************
>>
>>
>> IIS has crashed...
>> Beginning Analysis
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for
>> C:\WINDOWS\crystal\Emfgen.dll -
>> DLL (!FunctionName) that failed: Emfgen
>>
>>
>>
>>
>> Thread ID: 30
>> System Thread ID: 944
>> Kernel Time: 0:0:0.875
>> User Time: 0:0:10.843
>> Thread Type: Other
>> # ChildEBP RetAddr
>> WARNING: Stack unwind information not available. Following frames may be
>> wrong.
>> 00 1050eeb0 5020726f Emfgen+0x146d
>> 01 66207365 00000000 0x5020726f
>> Closing open log file C:\iisstate\output\IISState-3032.log
>> Opened log file 'C:\iisstate\output\IISState-3032.log'
>>
>> ***********************
>> Starting new log output
>> IISState version 3.3.1
>>
>> Sat Feb 18 11:51:49 2006
>>
>> OS = Windows 2003 Server
>> Executable: w3wp.exe
>> PID = 3032
>>
>> Note: Thread times are formatted as HH:MM:SS.ms
>>
>> ***********************

RE: w3svc service crashes - something to do with Emfgen.dll

Dear Kelly,

Yes I found the solution. I was getting the problem due to old version of
rptserver.asp. So I downloaded the latest asp pages of crystal from Crystal
site and problem got resolved.

If you need the latest asp pages of crystal, kindly go on crystal site and
search for Crystal85Samples which contains all the latest asp pages.

Also just for your info this problem was in the Application Creat object
line.

I hope this resolves your problem.


"Kelly Bills" wrote:

> I am having the similiar problem. Did you find the solution?
>
> Thanks.
>
> "Tanveer Ansari" wrote:
>
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Sat Feb 18 11:50:57 2006
> >
> > OS = Windows 2003 Server
> > Executable: w3wp.exe
> > PID = 3032
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> > IIS has crashed...
> > Beginning Analysis
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> > C:\WINDOWS\crystal\Emfgen.dll -
> > DLL (!FunctionName) that failed: Emfgen
> >
> >
> >
> >
> > Thread ID: 30
> > System Thread ID: 944
> > Kernel Time: 0:0:0.875
> > User Time: 0:0:10.843
> > Thread Type: Other
> > # ChildEBP RetAddr
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 00 1050eeb0 5020726f Emfgen+0x146d
> > 01 66207365 00000000 0x5020726f
> > Closing open log file C:\iisstate\output\IISState-3032.log
> > Opened log file 'C:\iisstate\output\IISState-3032.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Sat Feb 18 11:51:49 2006
> >
> > OS = Windows 2003 Server
> > Executable: w3wp.exe
> > PID = 3032
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************