Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failed to connect to host: Connection broken

Status
Not open for further replies.

khalidaaa

Technical User
Joined
Jan 19, 2006
Messages
2,323
Location
BH
Hi all,

I have problem with one of our Windows 2003 servers and i would appreciate any help.

I get this error on one of our applications when they try to access:


When i checked the event viewer i got this message:


Yesterday i observe that I got this message when i run our backup script (which runs every night) So i'm not sure if this related to our backup somehow! and these are the errors I got on the event viewer:

Code:
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x8007041d]

For more information, see Help and Support Center at 
[URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

Code:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007041d.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

Code:
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x8007041d]

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

Code:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance( CLSID_VSSCoordinator, IID_IVssShim).  hr = 0x8007041d.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

The source for the above errors was VSS

Code:
End Operation: Warnings or errors were encountered. 
Consult the backup report for more details.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

The Source of the above error was ntbackup

Code:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. 

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

And that's the final error (in the sequnce above) which i just showed above in the pic link!

Any help would be appreciated.

Regards,
Khalid
 
Thanks Hasan for the input but first of all the document mentioned that both of these errors should appear as simptoms to this problem:

Code:
Event ID: 1054
Source: Userenv
Type: Error

Description: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or exist or could not be contacted). Group Policy processing aborted.

Data: (unavailable) 
-and- 
Event ID: 1000
Source: UserInit
Type: Error

Description: Could not execute the following script AdminPassword.bat. The system cannot find the file specified.

Data: (unavailable)

The other thing in the next page of the same document you proposed it is saying that this resolution for a cluster machine!

Code:
Note Microsoft Windows Server 2003 supports Media Sensing when it is used in a server cluster environment. By default, however, Media Sensing is disabled in a Windows Server 2003-based server cluster, and the DisableDHCPMediaSense registry entry has no effect. In Windows Server 2003 Service Pack 1 (SP1), the DisableClusSvcMediaSense registry entry was introduced. You can use this registry entry to enable Media Sensing on the Windows Server 2003-based nodes of a server cluster.

and it says that the Media Sensing is disabled in Windows 2003-based server!

So I'm still in doubt of applying this solution coz this is a production system!

The only resolution to this problem i found so far is to reboot the system! but this doesn't fix the problem for so long coz it just comes back again!

Any other suggestions?

Regards,
Khalid
 
Thanks Hasan for your help but still that link, though close somehow to my problem, is not explaining my environment! we have Windows 2003 DCs!

Regards,
Khalid
 
Take any Event ID Errors to this site and poke around in there.




Group Policy may not install the PolicyMaker Software Update client on a Windows XP Service Pack 2-based computer, and event ID 5719 and event ID 1054 are logged

A Microsoft Windows Server 2003-based server may experience time-stamp counter drift if the server uses dual-core AMD Opteron processors or multiprocessor AMD Opteron processors
 
Thanks linney for the nice links!

I tried to apply some of the suggestions from your links. I just couldn't find that problem reoccuring again! so i thought of waiting till i get the simptoms again!

Regards,
Khalid
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top