|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I have been getting this Event 27745 Error (Source: Windows SharePoint
Services 3). I checked EventID.Net and it says, "No information found. If you
have additional information about this event please send it to us.
The submitted events will be forwarded to Altair Technologies consultants
for analysis.
We recommend however, that you first check the EventID.Net Processing Queue
to see if the event was already submitted by another contributor."
Anyway, my error reads,
The description for Event ID ( 27745 ) in Source ( Windows SharePoint
Services 3 ) 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: #50071: Unable to connect to the database STS_TSMAIL_1 on
TSMAIL\MICROSOFT##SSEE. Check the database connection information and make
sure that the database server is running..
I have been receiving a lot of errors from SharePoint Services 3 lately...
Had anyone experience this before?
|
|
To add on, I also received Event 6398, 5215 and 3760 errors, all from
SharePoint together...
Event 6398:
Category: Timer
The Execute method of job definition
Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition (ID
1535b2e8-47ab-4185-b803-b6ba8f0138ff) threw an exception. More information is
included below.
Unable to connect to database. Check database connection information and
make sure the database server is running.
Event 5215:
Category: Timer
Unable to connect to database. Check database connection information and
make sure the database server is running.
Event 3760:
Category: Database
SQL Database 'STS_TSMAIL_1' on SQL Server instance
'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error
information from SQL Server is included below.
Cannot open database "STS_TSMAIL_1" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
I also received Event 18456 Failure Audit that reads,
The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
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:
NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>].
"wrytat" wrote:
[Quoted Text] > I have been getting this Event 27745 Error (Source: Windows SharePoint
> Services 3). I checked EventID.Net and it says, "No information found. If you
> have additional information about this event please send it to us.
> The submitted events will be forwarded to Altair Technologies consultants
> for analysis.
> We recommend however, that you first check the EventID.Net Processing Queue
> to see if the event was already submitted by another contributor."
>
> Anyway, my error reads,
> The description for Event ID ( 27745 ) in Source ( Windows SharePoint
> Services 3 ) 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: #50071: Unable to connect to the database STS_TSMAIL_1 on
> TSMAIL\MICROSOFT##SSEE. Check the database connection information and make
> sure that the database server is running..
>
> I have been receiving a lot of errors from SharePoint Services 3 lately...
> Had anyone experience this before?
>
|
|
I'm seeing the same errors. Did you find a solution?
Thanks,
bc
"wrytat" wrote:
[Quoted Text] > To add on, I also received Event 6398, 5215 and 3760 errors, all from
> SharePoint together...
>
> Event 6398:
> Category: Timer
> The Execute method of job definition
> Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition (ID
> 1535b2e8-47ab-4185-b803-b6ba8f0138ff) threw an exception. More information is
> included below.
>
> Unable to connect to database. Check database connection information and
> make sure the database server is running.
>
> Event 5215:
> Category: Timer
>
> Unable to connect to database. Check database connection information and
> make sure the database server is running.
>
> Event 3760:
> Category: Database
> SQL Database 'STS_TSMAIL_1' on SQL Server instance
> 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error
> information from SQL Server is included below.
>
> Cannot open database "STS_TSMAIL_1" requested by the login. The login failed.
> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
>
> I also received Event 18456 Failure Audit that reads,
>
> The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
> 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:
> NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>].
>
> "wrytat" wrote:
>
> > I have been getting this Event 27745 Error (Source: Windows SharePoint
> > Services 3). I checked EventID.Net and it says, "No information found. If you
> > have additional information about this event please send it to us.
> > The submitted events will be forwarded to Altair Technologies consultants
> > for analysis.
> > We recommend however, that you first check the EventID.Net Processing Queue
> > to see if the event was already submitted by another contributor."
> >
> > Anyway, my error reads,
> > The description for Event ID ( 27745 ) in Source ( Windows SharePoint
> > Services 3 ) 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: #50071: Unable to connect to the database STS_TSMAIL_1 on
> > TSMAIL\MICROSOFT##SSEE. Check the database connection information and make
> > sure that the database server is running..
> >
> > I have been receiving a lot of errors from SharePoint Services 3 lately...
> > Had anyone experience this before?
> >
|
|
No luck... And now I'm getting 1 more error from SharePoint Services 3...
Event 3355. Cannot connect to SQL Server. TSMAIL\MICROSOFT##SSEE not found.
Additional error information from SQL Server is included below.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
We are worried that the SharePoint Services would crash one day, yet we
could not find a solution... And we also don't know how to restore, say an
individual file, or a individual SharePoint website from the backup software
(BackupExec) that we are now using. So we have given up on SharePoint.
"Bob C" wrote:
[Quoted Text] > I'm seeing the same errors. Did you find a solution?
>
> Thanks,
> bc
>
> "wrytat" wrote:
>
> > To add on, I also received Event 6398, 5215 and 3760 errors, all from
> > SharePoint together...
> >
> > Event 6398:
> > Category: Timer
> > The Execute method of job definition
> > Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition (ID
> > 1535b2e8-47ab-4185-b803-b6ba8f0138ff) threw an exception. More information is
> > included below.
> >
> > Unable to connect to database. Check database connection information and
> > make sure the database server is running.
> >
> > Event 5215:
> > Category: Timer
> >
> > Unable to connect to database. Check database connection information and
> > make sure the database server is running.
> >
> > Event 3760:
> > Category: Database
> > SQL Database 'STS_TSMAIL_1' on SQL Server instance
> > 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error
> > information from SQL Server is included below.
> >
> > Cannot open database "STS_TSMAIL_1" requested by the login. The login failed.
> > Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
> >
> > I also received Event 18456 Failure Audit that reads,
> >
> > The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
> > 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:
> > NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>].
> >
> > "wrytat" wrote:
> >
> > > I have been getting this Event 27745 Error (Source: Windows SharePoint
> > > Services 3). I checked EventID.Net and it says, "No information found. If you
> > > have additional information about this event please send it to us.
> > > The submitted events will be forwarded to Altair Technologies consultants
> > > for analysis.
> > > We recommend however, that you first check the EventID.Net Processing Queue
> > > to see if the event was already submitted by another contributor."
> > >
> > > Anyway, my error reads,
> > > The description for Event ID ( 27745 ) in Source ( Windows SharePoint
> > > Services 3 ) 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: #50071: Unable to connect to the database STS_TSMAIL_1 on
> > > TSMAIL\MICROSOFT##SSEE. Check the database connection information and make
> > > sure that the database server is running..
> > >
> > > I have been receiving a lot of errors from SharePoint Services 3 lately...
> > > Had anyone experience this before?
> > >
|
|
|