Re: Error with .Net Runtime 2.0 on Windows Service
- From: "Microsoft News" <Name@xxxxxxxxxxx>
- Date: Wed, 3 Jan 2007 11:02:30 -0600
Update I think we have a clue about what is going on but not sure how to
prove it. When the window service is running and no one is making calls to
the Remoting DLL then there is no errors. But when users start using the
Remoting DLL calls then we get the error. The error seems to be random when
it occurs. I wonder if the issue is that the Window Service was created in
..Net 2005 and the Remoting DLL was created in .Net 2003?
If Microsoft reads these post, I wonder if they can tell me if .Net 2005
does not like working with .Net 2003
Clyde
"Microsoft News" <Name@xxxxxxxxxxx> wrote in message
news:Oi5Hrm7KHHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
I need some serious help. I am getting the following errors in my event
log:
Source: .NET Runtime 2.0 Error Event ID: 5000
EventType clr20r3, P1 orionnetreg.exe, P2 1.3.2548.24224, P3 458d8320, P4
system, P5 2.0.0.0, P6 4333ae87, P7 374c, P8 124, P9
system.objectdisposedexception, P10 NIL.
Source: .NET Runtime 2.0 Error Event ID: 5000
EventType clr20r3, P1 orionnetreg.exe, P2 1.3.2548.27502, P3 458d9cbd, P4
system.data, P5 2.0.0.0, P6 4333aea2, P7 1946, P8 25, P9
system.invalidoperationexception, P10 NIL.
The first one I might have fixed because it has gone away but the other
error keeps happening. I took a window service created in VB .Net 2003
that had worked like a charm. What the service did was expose a Remoting
DLL that a windows application called and it had a timer that would
trigger every so often and then the service would make some calls to some
web services created with WSE 2.0. I updated the code to .Net 2005, then
updated the web services calls to WSE 3.0 and had no errors or anything.
I reinstalled the service and started it up with no problem. Then after
the windows application connected to the Remoting calls the service would
DIE with the error at the top. After a lot of work and testing I realize
that the problem was some COM DLLs that had not registered correctly so
after Unregistring them and re-registering them that error went away.
Then I deployed my service out to my customers computer after 10 days of
letting it run and testing on my server. My server is Windows 2003 Small
Business Standard server with all of its UPDATE.
I installed it on 9 customers servers. All different servers, some
Windows 2000, some XP Pro, and some Windows 2003 Small business standard.
7 repeatly have the second error listed above, the only two that do not
have the issue, one is a Windows 2003 server and the other is a 2000
server. I have tried putting logging into the code, it logs fine but then
dies for no reason. I can not find when it dies, and the message above is
CRAP!!!! (For give my frustration)
We have tried everything, my server and two other work with no problem.
But I don't know why these messages are only showing up on some servers
and I can not get any reliable message to tell me what is going on. I see
that it has something with System.Data, and that it is some System.Invalid
Operation Exception but I can not get any more dumpped out.
Anyone out there who can help me with this. We are dead in the water if
we can not fix this. It seems to be something with .Net 2.0 but
WHAT????????????
ALL HELP appriecated.
Clyde
.
- Prev by Date: Re: Remoting Security
- Next by Date: Re: Last Stop Before Support Call
- Previous by thread: Re: Remoting Security
- Next by thread: Re: Last Stop Before Support Call
- Index(es):
Relevant Pages
|
