Disconnect Issues & RPC Server Unavailable

We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
We had a similar problem after upgrading clients to XP SP2, the problem
turned out to be the MDAC version that ships with SP2. Apparently, the new
version of MDAC has issues keeping a connection with the DB if it is using
named pipes. An example of this is when we would run a restore with QA using
the normal connection to a server(named pipes) it would die and say
something about a disconnect even though ping is at 100%. As soon as we
forced tcp/ip on QA everything worked fine. Might try setting up an alias to
the server using tcp/ip to see if that makes a difference.
KevinE
"Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
> We have recently upgraded our main server from NT4 to Active Directory
> (Windows 2003 Server). Our SQL Database is 2000 and is running on a
> Windows
> 2000 Server Box. We use com+ components to connect to our database.
> Since
> the change on our PDC to 2003 Server AD, we have had several errors such
> as
> "The object invoked has disconnected from its clients" as well as RPC
> Server
> Unavailable. This occurs even when the user is consistently active. We
> have
> applied latest Windows Service Pack to clients xp sp2 and to the windows
> 2000
> server box. If you reboot the server and or/stop services (Com+ and Dcom)
> on
> the client end, they can get back in. You can browse to the machine no
> problem through exporer - right to the database. Issue is only in SQL
> 2000.
> Any assistance would be greatly appreciated. Note: I have also checked
> using netstat -a to see if all ports were being used and that is not the
> case. This is happening on more than one users connection and I am
> certain
> it is not network based - ping 100%, can browse, two locations within
> building etc.
|||The issue is regardless of sp1 or 2. Any error logs you can suggest for me
to look at?
Thank you
"KevinE" wrote:

> We had a similar problem after upgrading clients to XP SP2, the problem
> turned out to be the MDAC version that ships with SP2. Apparently, the new
> version of MDAC has issues keeping a connection with the DB if it is using
> named pipes. An example of this is when we would run a restore with QA using
> the normal connection to a server(named pipes) it would die and say
> something about a disconnect even though ping is at 100%. As soon as we
> forced tcp/ip on QA everything worked fine. Might try setting up an alias to
> the server using tcp/ip to see if that makes a difference.
> KevinE
> "Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
> news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
>
>