RE: Runtime Error!
- From: "duncans" <duncans@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Dec 2005 21:43:02 -0800
Makes sense. After I posted my last note on this thread I spent almost 3
hours on the phone with Microsoft support on this specific issue.
Being bored after the first couple of hours I googled the problem while the
tech was futzing around with my system (via Live Meeting which is pretty
cool) and found a KB article, Q309694, that describes the problem.
Unfortunately, the 'fixes' in the KB article tell how to modifiy programs to
avoid the error--which is not much help from an end users point of view.
My guess was a mashed DLL--or perhaps an incorrect version of a DLL. The
tech seemed to think that the problem had something to do with my settings in
SBS. This seemed unlikely as I was getting the error on restart related to an
app named 'dredger.exe'.
In any case, we finally escalated the issue to a senior tech and he
suggested taking a look at the installed versions of .NET framework. It
turned out that versions were correct but he suggested that we reinstall
updates to 1.1 and reinstall 2.0. (I reminded him that we couldn't downolad
and install updates as we would get the same error!) As more or less a last
resort we decided to do a repair on 2.0. Surprise! Not only did my server
reboot without error but I was able to complete the ICW and problems I had
been having with the firewall and secure Web site configuration went away, as
well.
Again, there may be multiple root causes for this particular error but you
might want to try the .NET repair route. It does appear that at least one DLL
was corrupt or missing from the .NET install.
--
Duncan Sutherland
"Warren Pierro" wrote:
> No,
> Susan gave me a registry fix but I am hesitating to use it. I really want to
> know why this happened from Microsoft.
> I installed my SBS 2003 offline and did all the updates and SPs before it
> was connected to any clients. The problem installation I need help with is in
> a working medical office and I really can't afford to take down the server.
> --
> procompserv
>
>
> "duncans" wrote:
>
> > Warren, did you get a fix to the problem you describe? Susan is usually right
> > on the money <g> so before I start reinstalling the installer I wanted to
> > check to see if the KB she referenced was indeed the issue that was causing
> > your problems. I am having exactly the same issue (same error message).
> > Thanks!
> > --
> > Duncan Sutherland
> >
> >
> > "Warren Pierro" wrote:
> >
> > > I reciently installed SBS 2003 standard on a Dell server. All went well until
> > > I tried to install the SP1 and related updates. Server 2003 SP1 installed OK.
> > > When I tried to install Share Point Services 2.0 it fails and I get a runtime
> > > error (C:\WINDOWS\system32\msiecxec.exe - This application has requested the
> > > runtime to terminate it in an unusual way. Please contact the application's
> > > support team for more information.)
> > > I tried to do the Exchange update and recieved the same message.
> > >
> > > I am using remote desktop to administer this server.
> > > --
> > > Warren Pierro
.
- Prev by Date: Re: Keep admins off of client machines
- Next by Date: Re: after sharepoint 2.0 update
- Previous by thread: Re: Runtime Error!
- Next by thread: Re: Crazy backup recovery... if possible.
- Index(es):
Relevant Pages
|
