ID de evento do Analysis Services e descrições de eventos (pt-BR)

ID de evento do Analysis Services e descrições de eventos (pt-BR)

Esse artigo foi originalmente escrito em: Analysis Services Event ID and Event Descriptions

Essas IDs de evento e descrições de evento são para SQL Server Analysis Services (SSAS), uma ferramenta do SQL Server.

Aplica-se a: SQL Server 2005 (exceto quando indicado), SQL Server 2008, SQL Server 2008 R2, SQL Server  Code-named“Denali”.
 Para obter mais informações sobre erros de evento específico, acesse http://eventid.net/.  A origem do evento é MSSQLServerOLAPService.
ID do Evento
Nível
Descrição
0
Informational
Service started successfully.
1
Informational
Service stopped.
2
Informational
The system is out of memory.
3
Informational
The query log was started.
4
Informational
The query log was stopped.
5
Informational
The flight recorder was started.
6
Informational
The flight recorder was stopped.
7
Informational
The data mining algorithm provider <providername> for the <algorithmname> algorithm was loaded.
8
Informational
The error log was started.
9
Informational
The error log was stopped.
 
ID do Evento
Nível
Descrição
0
Warning
The data mining algorithm provider <providername> for the <algorithmname> algorithm cannot be loaded.
 
ID do Evento
Nível
Descrição
0
Error
The service cannot be started:  <servicename>
1
Error
<error message from Message Manager>.
3
Error
<error message from OLE DB provider>.
4
Error
An error occurred while starting the flight recorder.
5
Error
An error occurred while the query log table was being created. Check the query log connection string, permissions, or the query log database for problems:
6
Error
An error occurred while data was being written to the query log. Although the table was created, query logging has stopped. Check the query log database or permissions for issues:
7
Error
An error occurred while starting the query log.
8
Error
The operating system resource (event) could not be created during initialization of the lazy writer.
9
Error
The operating system resource (thread) could not be created during the initialization of the lazy writer.
10
Error
An error occurred while closing the trace output file, <filename>.
11
Error
An error occurred while writing a trace event to the file, <filename>.
12
Error
An error occurred while writing a trace event to the rowset.
13
Error
The trace timed out while waiting for the TCP rowset sender to finish.
14
Error
An error occurred when the service attempted to shrink the database connection pool.
15
Error
An error occurred while stopping the query log.
16
Error
An error occurred while starting the error log.
17
Error
An error occurred while stopping the error log.
18
Error
<error message about instantiating metadata object>
19
Error
<error message about loading metadata object>
20
Error
Lazy processing failed because of the following error:  <errormessage>
21
Error
The configuration file could not be loaded. The file may be damaged or contain XML that is not valid. <filename>
22
Error
The configuration file could not be saved. The file may be locked by another program. <filename>
23
Error
The database cryptographic key could not be loaded: <filename>
24
Error
The metadata object could not be linked.
25
Error
The resource file '<filename>’ for locale ‘<localename>’ could not be loaded. Switching to US English (1033) if available.
26
Error
Unable to find or start SQLSQM.EXE successfully.
27
Error
Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc.
28
Error
Failed to load server config file: setting <settingname> containing value=<valuename> is incorrect. Use msmdsrv.bak to restore msmdsrv.ini.
29
Error
Failed to load server plug-in extension defined in assembly ‘<assemblyname>’. The following error(s) have been raised during the plug-in initialization. <errormessage>
NOTA: Este evento não se aplica ao SQL Server 2005.
30
Error
The database cannot be attached because an error occurred while loading the detach log from the file '<filename>'. One possible reason is that database is already attached in ReadWrite mode to another server instance.
NOTA: Este evento não se aplica ao SQL Server 2005.
31
Error
The file ‘<filename>' could not be deleted. Please check the file for permissions.
32
Error
The directory '<directoryname>' could not be deleted. Please check the directory for permissions.
33
Error
File or folder '<file/foldername> could not be moved. It may be locked by indexing or antivirus software.
NOTA: Este evento não se aplica ao SQL Server 2005.
34
Error
An error occurred during transaction rollback (HRESULT=<HRESULTCODE>).
NOTA: Este evento não se aplica ao SQL Server 2005.
35
Error
The file '<filename> could not be opened. Please check the file for permissions or see if other applications locked it.
36
Error
Unable to commit Synch transaction safely; server is forced to shutdown; old DB with ID='<ID>'will be recovered during server startup.
NOTA: Este evento não se aplica ao SQL Server 2005.
37
Error
Cannot start the server in Vertipaq mode as the needed privilege for memory locking is not held (SE_INC_WORKING_SET_NAME or SE_INC_BASE_PRIORITY_NAME, depending on your operating system version).
NOTA: Este evento não se aplica ao SQL Server 2005.
 


Veja Também



Outros Idiomas

Este artigo está igualmente disponível nos seguintes idiomas:

Inglês (en-US)

 

Leave a Comment
  • Please add 4 and 5 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Carsten Siemens edited Revision 1. Comment: fixed typo

Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Carsten Siemens edited Revision 1. Comment: fixed typo

Page 1 of 1 (1 items)