.Net Framework runtime errors
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
.Net Framework runtime errors

 
Post new topic   Reply to topic    Windows Server Forum Index -> Small Business Server 2003
Author Message
Gary Karasik
Guest





Posted: Sun Jan 16, 2005 7:30 am    Post subject: .Net Framework runtime errors Reply with quote

Hi,

One of my SBS 2K3 servers is giving the following errors when trying to run
certain applications. Some Googling indicates that these are .Net Framework
errors. I've tried reapplying .Net Framework Service Pack 1 for Windows
Server 2003, but that didn't help. I'm afraid I might need to pay MS on this
one, but before I spend $245 of my client's money, I thought I'd take a shot
here. Anybody have any ideas about how to track this one down and resolve
it. The error shows up in a popup immediately on starting the apps. If I
click OK, the app terminates; if I click Cancel, it tries to find a
debugger. Maybe some files need to be restored or some DLL needs to be
reregistered, but this error doesn't give me much to go on.

TIA,

GaryK

==================================================================

ExBPA.exe - Common Language Runtime Debugging Services : Application has
generated an exception that could not be handled.

Process id=0x2540 (9536), Thread id=0x23c0 (9152).

Click OK to terminate the application.
Click CANCEL to debug the application.

=================================================================

V2iConsole.exe - Common Language Runtime Debugging Services : Application
has generated an exception that could not be handled.

Process id=0x24a4 (9380), Thread id=0x2484 (9348).

Click OK to terminate the application.
Click CANCEL to debug the application.

================================================================
Back to top
Susan Bradley, CPA aka Eb
Guest





Posted: Sun Jan 16, 2005 10:41 am    Post subject: Re: .Net Framework runtime errors Reply with quote

What's installed on this box besides the normal stuff? And what app are
you running on the server?

Gary Karasik wrote:
Quote:
Hi,

One of my SBS 2K3 servers is giving the following errors when trying to run
certain applications. Some Googling indicates that these are .Net Framework
errors. I've tried reapplying .Net Framework Service Pack 1 for Windows
Server 2003, but that didn't help. I'm afraid I might need to pay MS on this
one, but before I spend $245 of my client's money, I thought I'd take a shot
here. Anybody have any ideas about how to track this one down and resolve
it. The error shows up in a popup immediately on starting the apps. If I
click OK, the app terminates; if I click Cancel, it tries to find a
debugger. Maybe some files need to be restored or some DLL needs to be
reregistered, but this error doesn't give me much to go on.

TIA,

GaryK

==================================================================

ExBPA.exe - Common Language Runtime Debugging Services : Application has
generated an exception that could not be handled.

Process id=0x2540 (9536), Thread id=0x23c0 (9152).

Click OK to terminate the application.
Click CANCEL to debug the application.

=================================================================

V2iConsole.exe - Common Language Runtime Debugging Services : Application
has generated an exception that could not be handled.

Process id=0x24a4 (9380), Thread id=0x2484 (9348).

Click OK to terminate the application.
Click CANCEL to debug the application.

================================================================



--
An open letter to the Security Community::
http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
Back to top
Gary Karasik
Guest





Posted: Sun Jan 16, 2005 12:49 pm    Post subject: Re: .Net Framework runtime errors Reply with quote

Quote:
What's installed on this box besides the normal stuff?

Nothing special that I'm aware of, nothing on this particular server that
isn't running on several others.

Quote:
And what app are you running on the server?

The two apps that are problematic are Exchange Best Practices Analyzer and
V2i Protector.

I think either it's a corrupted DLL, or a permissions issue on some file in
some subdirectory that Net Framework needs to function. I've already done a
partial reinstall of Net Framework (not easy with Windows Server 2003
because Net Framework is treated as part of the OS, and I've done a
reinstall of Net Framework 1.l Service Pack 1.

Trouble-shooting this is made very difficult by the fact that the error
doesn't provides insufficient info, basically just, "I'm not going to work.
Goodbye."

Is there an equivelant to XP's SFC /SCANNOW on SBS 2003?

GaryK

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:%23angbW4%23EHA.4004@tk2msftngp13.phx.gbl...
Quote:
What's installed on this box besides the normal stuff? And what app are
you running on the server?

Gary Karasik wrote:
Hi,

One of my SBS 2K3 servers is giving the following errors when trying to
run certain applications. Some Googling indicates that these are .Net
Framework errors. I've tried reapplying .Net Framework Service Pack 1 for
Windows Server 2003, but that didn't help. I'm afraid I might need to pay
MS on this one, but before I spend $245 of my client's money, I thought
I'd take a shot here. Anybody have any ideas about how to track this one
down and resolve it. The error shows up in a popup immediately on
starting the apps. If I click OK, the app terminates; if I click Cancel,
it tries to find a debugger. Maybe some files need to be restored or some
DLL needs to be reregistered, but this error doesn't give me much to go
on.

TIA,

GaryK

==================================================================

ExBPA.exe - Common Language Runtime Debugging Services : Application has
generated an exception that could not be handled.

Process id=0x2540 (9536), Thread id=0x23c0 (9152).

Click OK to terminate the application.
Click CANCEL to debug the application.

=================================================================

V2iConsole.exe - Common Language Runtime Debugging Services : Application
has generated an exception that could not be handled.

Process id=0x24a4 (9380), Thread id=0x2484 (9348).

Click OK to terminate the application.
Click CANCEL to debug the application.

================================================================

--
An open letter to the Security Community::
http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
Back to top
Bob P
Guest





Posted: Sun Jan 16, 2005 7:51 pm    Post subject: Re: .Net Framework runtime errors Reply with quote

Try running the app from a command line like this:

app.exe > c:\error.log



On Sat, 15 Jan 2005 22:49:55 -0800, "Gary Karasik" <gkarasik2fea.net>
wrote:


Quote:
Trouble-shooting this is made very difficult by the fact that the error
doesn't provides insufficient info, basically just, "I'm not going to work.
Goodbye."
Back to top
Gary Karasik
Guest





Posted: Sun Jan 16, 2005 7:51 pm    Post subject: Re: .Net Framework runtime errors Reply with quote

Thanks, Bob. The resulting ERROR.TXT is blank.

GaryK

"Bob P" <rpalnik@metfabtech.com> wrote in message
news:0vvku0l9te2ton1rp61n16m6hqao7bibgd@4ax.com...
Quote:
Try running the app from a command line like this:

app.exe > c:\error.log



On Sat, 15 Jan 2005 22:49:55 -0800, "Gary Karasik" <gkarasik2fea.net
wrote:


Trouble-shooting this is made very difficult by the fact that the error
doesn't provides insufficient info, basically just, "I'm not going to
work.
Goodbye."

Back to top
Bob P
Guest





Posted: Mon Jan 17, 2005 12:18 am    Post subject: Re: .Net Framework runtime errors Reply with quote

Well, so much for that idea!

On Sun, 16 Jan 2005 10:25:49 -0800, "Gary Karasik" <gkarasik2fea.net>
wrote:

Quote:
Thanks, Bob. The resulting ERROR.TXT is blank.

GaryK

"Bob P" <rpalnik@metfabtech.com> wrote in message
news:0vvku0l9te2ton1rp61n16m6hqao7bibgd@4ax.com...
Try running the app from a command line like this:

app.exe > c:\error.log



On Sat, 15 Jan 2005 22:49:55 -0800, "Gary Karasik" <gkarasik2fea.net
wrote:


Trouble-shooting this is made very difficult by the fact that the error
doesn't provides insufficient info, basically just, "I'm not going to
work.
Goodbye."


Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Small Business Server 2003 All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB