April 29, 2008 at 11:46 am
Hi,
here is the problem:
we have new cluster installed, i was not able to open the error log, message was that named pipes protocol is not configured for remote access.
i fixed the problem by creating an alias for named pipes protocol, where alias name is virtual machine name and for server part i specified cluster name.
It's a brand new installation, looks like something is wrong here, may be windows or sql bug? anyone had the same problem?
here is the error i was getting before fix:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 4/28/2008
Time: 1:46:44 PM
User: N/A
Computer: name
Description:
The description for Event ID ( 17052 ) in Source ( MSSQLSERVER )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from
a remote computer. You may be able to use the /AUXSOURCE= flag to
retrieve this description; see Help and Support for details.
The following information is part of the event: Severity: 16 Error:2,
OS: 2 [Microsoft][SQL Native Client]Named Pipes Provider:
Could not open a connection to SQL Server [2]. .
Data:
0000: 02 00 00 00 0a 00 00 00 ........
0008: 12 00 00 00 41 00 32 00 ....A.2.
0010: 53 00 51 00 4c 00 43 00 S.Q.L.C.
0018: 4c 00 33 00 00 00 0e 00 L.3.....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...
June 19, 2008 at 9:41 am
Yes ...
The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Severity: 16 Error:18456, OS: 18456 [Microsoft][SQL Native Client][SQL Server]Login failed for user ....
My collegue changes SID of the virtual machine where biztalk2006 is installed and after the reboot we can't
run the biztalk server... unfortunately we don't have any solution at the moment . it has happened this afternoon...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply