Problem after Server 2003 SP1

We had this 3-tier development environment (Web, App, DB) on Windows Server
2003 platform which works fine.

After installing the Service Pack 1 for Server2003, we encountered this
"error '800706be'" in the asp page. We pinpointed from the Event Viewer that
it is due to one of the components (in C++) having this Exception: E06D7363
error.

However, components coded in VB were fine and able to connect to be the DB.

We had tried verifying the security settings, esp with the new DCOM changes
in SP 1 and had given the account used for connecting web to app the
"Distributed COM" user group rights too.

We had also tried re-compiling the C++ component on machine with SP1
installed , but to no avail.

Greatly appreciate all assistance to solve this issue with the Server 2003
SP1.
Thanks.

Crossposted to windows.server.general, where you're more likely to get a
response

--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com/millsrpch.htm

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Fuji" <> wrote in message
newsE71B013-4DBD-4BF5-91F4-...
> We had this 3-tier development environment (Web, App, DB) on Windows
> Server
> 2003 platform which works fine.
>
> After installing the Service Pack 1 for Server2003, we encountered this
> "error '800706be'" in the asp page. We pinpointed from the Event Viewer
> that
> it is due to one of the components (in C++) having this Exception:
> E06D7363
> error.
>
> However, components coded in VB were fine and able to connect to be the
> DB.
>
> We had tried verifying the security settings, esp with the new DCOM
> changes
> in SP 1 and had given the account used for connecting web to app the
> "Distributed COM" user group rights too.
>
> We had also tried re-compiling the C++ component on machine with SP1
> installed , but to no avail.
>
> Greatly appreciate all assistance to solve this issue with the Server 2003
> SP1.
> Thanks.
>
>