Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  SSAS  [ 14 result(s) ]
MICROSOFT 
117   -  Unexpected fatal error occurred. Attempting to restart server.%0\r\n  MICROSOFT
The Analysis server has shut down. The application event log will contain a message that resembles the following: Source: MSSQLServerOLAPServices Event ID: 117 Description: Unexpected fatal error occurred. Attempting to restart server. In addition, Analysis Manager or a client application may display a message such as the following: Connection to the server is lost. Possible reasons for the shutdown include: The data files in the Analysis Services Data directory are corrupted. The server has encountered a bug.
To fix corrupted data files, stop the Analysis server if it is running, and then delete all files in the Data directory for Analysis Services. After you delete the files, restart the server and restore your Analysis Services databases from backup files. To correct possible bugs, make sure that your server is running the latest service pack for SQL Server 2000 Analysis Services. For more information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack.
SQL Server Analysis Services (SSAS)
Comments
 
123   -  The server is out of memory.%0  MICROSOFT
Analysis Services load all dimensions for all databases into volatile memory on startup. During processing, the server consumes additional memory to process updates to dimensions and cubes. If insufficient memory is available for these and other operations, you will receive this message.
You can resolve this issue in several ways: Using Microsoft Windows® NT 4.0 Enterprise Edition, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server, enable application memory tuning and then enable the Analysis server to use 3 gigabytes (GB) of RAM. For more information, see Microsoft Knowledge Base article 295443, How To Enable Analysis Services to Use 3 GB of RAM. Lower the HighMemoryLimit registry entry, so that the cleaner thread starts earlier. For more information on this, and other registry entries mentioned in this topic, see this Microsoft Web site. Lower the BackgroundInterval registry entry, so that background operations are performed more frequently. Lower the ProcessReadAheadSize, ProcessReadSegmentSize, and ProcessRecordsReportGranularity registry entries to reduce the amount of memory used during processing. Increase the page file size or create a second page file. If dimensions are too large to fit in memory, the following changes may be required: Install more physical memory in the server. Upgrade to a 64-bit platform. Reduce the size of the dimension as follows: Convert the dimension keys to integers. Eliminate any unnecessary redundant data elements. Delete or reduce the number of member properties used in dimensions. Convert to ROLAP storage.
SQL Server Analysis Services (SSAS)
Comments
 
2437   -  An unexpected internal error has occurred.  MICROSOFT
Analysis Services encountered a bug in either the server or the client software. The message shown earlier is a general message for this type of error.
Contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
3013, 30163, 30322, or 33031   -  Data source provider error: provider message  MICROSOFT
This message appears in the Event Viewer application log. Analysis Services returns this message after it accesses a relational data source during cube processing, ROLAP queries, cell or dimension writeback, mining model training, writing to the query log, or other processes. Any message returned by the data source provider is appended to the message.
In some cases, a data source may not support the syntax of a query. If the message returned by the provider indicates a syntax error, you may be able to reconfigure the data source to work around the problem. To find solutions for syntax errors or other known problems, you can search at Knowledge Base (KB) Search. for the provider message returned with the error message. If you are unable to resolve this problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
3151   -  The user could not be authenticated.  MICROSOFT
Analysis Services returns this message when a client attempts to connect to the server and the server is unable to authenticate the client. This usually occurs if the client and the server are in different Microsoft Windows® domains that do not have a trust relationship. This message can also appear when a client is trying to connect over the Internet.
Ensure that there is a trust relationship between the server and the client domains. If establishing a trust relationship is not possible, use an HTTP connection between the client and the server. The following articles on the Microsoft Web site describe how to connect to Analysis Services over the Internet: Microsoft Support WebCast: How to Connect to Analysis Services over the Internet (http://support.microsoft.com/servicedesks/webcasts/wc120401/wct120401.asp) Improved Web Connectivity in Microsoft SQL Server 2000 Analysis Services (http://go.microsoft.com/fwlink/?LinkId=20292) MSDN: Build an OLAP Reporting App in ASP.NET Using SQL Server 2000 Analysis Services and Office XP (http://go.microsoft.com/fwlink/?LinkId=20293)
SQL Server Analysis Services (SSAS)
Comments
 
3238   -  Connection to the server is lost.  MICROSOFT
The client has lost its connection with the server and cannot reconnect. Possible reasons include the following: Dimension security evaluated to an empty dimension, preventing the server from continuing to send results to the client. A network problem exists between the client and the server. The server was stopped. The server is out of memory. The server has encountered a bug.
Perform the following tasks to resolve the problem: Ensure that you have the latest SQL Server 2000 Analysis Services service pack installed. If the connection was lost because the server could not continue sending the results to the client, verify that dimension security is configured properly. Troubleshoot the network connection between the client computer and the server. Ensure that the server is running and that the MSSQLServerOLAPService service is started. Check the event log to determine if the server has run out of memory. If you are unable to resolve this problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
30159   -  Error(%s1): The object structure is not valid (%s2) Invalid procedure call or argument.  MICROSOFT
Analysis Services encountered a bug.
Contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
30973   -  Unable to browse the cube '%s1'. Unable to open connection.  MICROSOFT
When you attempt to browse a cube, the connection to the server can be lost. Additionally, you cannot browse the cube with Analysis Manager when the All Caption property for the dimension matches the name of a level in the dimension.
Perform the following tasks to resolve the problem: Ensure that you have the latest SQL Server 2000 Analysis Services service pack installed. Troubleshoot the network connection between the client computer and the server. If you change the default setting for All Caption property, ensure that the new name does not match the name of any level in the dimension. By default, Analysis Services chooses a unique name for the All Caption property. If you are unable to resolve this problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
30979   -  Unable to browse the dimension '%s1'. The operation requested failed due to timeout.  MICROSOFT
By default the OLE DB time-out property is set to 15 seconds. If the query takes longer than 15 seconds to return data, the Analysis Manager browser returns the time-out message. Although you can set the default OLE DB time-out value in the connection string for ADOMD and OLE DB applications, you cannot configure this value for the Analysis Manager browser.
Install the latest SQL Server 2000 Analysis Services service pack, which increases the OLE DB time-out property to 30 seconds. Work with your network administrator to tune the network and reduce query response time.
SQL Server Analysis Services (SSAS)
Comments
 
-2147221453   -  Unable to connect to the registry on the server computer (), or you are not a member of the OLAP Administrators group on this server.  MICROSOFT
This error can occur for one of the following reasons: The user account used to connect to the Analysis server, using either Analysis Manager or a Decision Support Objects (DSO) application, is not a member of the OLAP Administrators group. You attempt to remotely administer a server that has been upgraded to Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3) from Analysis Manager or from any Decision Support Objects (DSO) application that has not been upgraded to SP3. The Remote Registry service is not started on an Analysis server that is running on Windows 2000.
You can take the following actions to resolve this problem: Obtain the latest service pack for SQL Server 2000. For additional information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack. Ensure that the user account used to connect to the Analysis server is a member of the OLAP Administrators group. For additional information, see Microsoft Knowledge Base article 231951, Permissions That You Must Have to Administer an OLAP Server. Note You may receive additional errors if the user account is not a member of the Administrators group. For additional information, see Microsoft Knowledge Base article 293782, Can Only Administer Analysis Server if User is a Member of Administrators Group. Ensure that the Remote Registry service is started if the Analysis server is running on Windows 2000. If you are unable to resolve this problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
 

 
SQL Server Analysis Services (SSAS) (14)
 
  Prev   1  2  Next