.net SP1 problem

Support, Questions and Discussions on WinSyslog

Moderator: alorbach

.net SP1 problem

Postby Clay on Tue Apr 15, 2003 12:50 am

I'll send you the information you ask for very soon.

The error dialog appears as soon as I reboot ... before ANY other applications are started (unless some auto start application causes it).

I have "sent" the error report to Microsoft, like the dialog asks for, so they have a copy of the error.

Thanks again .... Clay
Clay
 

Postby rgerhards on Tue Apr 15, 2003 9:11 am

Hi Clay,

OK, this clarifies a lot. I have to admit we do not yet have an idea of what exactly happened, but at least we now know where we can look into. BTW: the dump file you send will not be forwarded from Microsoft to us, so we are unfortunatley unable to request that data.

I keep you posted.

Rainer Gerhards
Adiscon
User avatar
rgerhards
Site Admin
 
Posts: 1282
Joined: Thu Feb 13, 2003 11:57 am

Postby Clay on Tue Apr 15, 2003 3:45 pm

Is there any way I can send the dump to you? I looked at the options but it didn't appear there was a way to change where the file was going. Is it captured on disk somewhere?
Clay
 

Postby alorbach on Tue Apr 22, 2003 12:03 pm

Unfortunately, the error report is only generated in memory, and not saved on harddisk. But if you click on details next time, you should get the error report as plain text. And then you can copy it into your clipboard, and send it to support@adiscon.com.
User avatar
alorbach
Site Admin
 
Posts: 855
Joined: Thu Feb 13, 2003 11:55 am

Postby Clay on Tue Apr 22, 2003 1:15 pm

I have done this and e-mail it to your support account.

Thanks - Clay
Clay
 

Postby Clay on Mon Apr 28, 2003 4:59 pm

Did you get my e-mail on this problem? Does it help?
Clay
 

Postby alorbach on Mon Apr 28, 2003 5:05 pm

Hi,

i wroet an answer to your email, you possible did not recieve it.
So I post it here again ;):


Hi,

thank you for the screenshots. If you click on the detaillinks on the second window, you will get more detailed information you can copy and paste in an email and send to us. This would be very helpful as well, because then we will see the memory addresses where the exception occurs.

Thanks for your patience - best regards,
Andre Lorbach

User avatar
alorbach
Site Admin
 
Posts: 855
Joined: Thu Feb 13, 2003 11:55 am

Postby Clay on Mon Apr 28, 2003 10:55 pm

The second screen shot does show the address where the error occured (offset 374C)... there is no more screen shots that appear or that I can link to.

Sorry.

Clay
Clay
 

Postby alorbach on Tue Apr 29, 2003 8:49 am

Strange, maybe something has changed.
But according to the screenshots, there are two debug files generated.
Is it possible to send them as well? That would be really helpful.
User avatar
alorbach
Site Admin
 
Posts: 855
Joined: Thu Feb 13, 2003 11:55 am

Postby Clay on Thu May 08, 2003 1:27 pm

After reinstalling winsyslog everything is working again. I don't know if other Microsoft patches fixed their problem or something else.

Thanks for your time.
Clay
 

Postby alorbach on Thu May 08, 2003 2:30 pm

Hi,

I am glad that this strange problem has solved itself with a reinstall.
Seems like that some Microsoft Patch was the Problem ;)
User avatar
alorbach
Site Admin
 
Posts: 855
Joined: Thu Feb 13, 2003 11:55 am

Google Ads



Return to WinSyslog

Who is online

Users browsing this forum: No registered users and 0 guests

cron