Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  SQL Server Analysis Services (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
 
-2147221453   -  Unable to connect to the registry on the server computer (<server name>), 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
 
31040 and 31041   -  Connection to server failed. Errors occurred while connecting to server name. Server message Do you still want to register this server?  MICROSOFT
A connection to a server can fail for various reasons. The following reasons are common: The user does not have the permissions required to access a server or a database. The repository is located on a remote computer, and the computer name cannot be resolved. The repository has been migrated to a SQL Server database, but the client is missing the necessary SQL Server connectivity components. A client does not have the permissions required to access the instance of SQL Server containing the database. Analysis Manager (or another application using DSO) is attempting to connect to an Analysis server with a later service pack than the Analysis Services service pack on the local host server. Network problems prevent the connection. These messages can also appear when the SQL Server Client Network Utility on the computer running Analysis Manager is configured to use TCP/IP as the default protocol, or if TCP/IP is used for the connection to the instance of SQL Server containing the Analysis Services repository. The error messages then indicate that Analysis Manager cannot make trusted connections with SQL Server using TCP/IP.
Examine the server message text embedded in the message for an indication of the problem. To see if there is a Knowledge Base article about the issue, you can search for the static portion of the server message string (omitting dynamic elements, such as a server name) at Knowledge Base (KB) Search. Ensure that the user or the client application has the permissions required to access the server, the database, and the repository, and that other connectivity problems do not exist between the client, the server, and the repository. If you are attempting to administer an upgraded Analysis server from an Analysis server that has not been upgraded, you can fix this problem by upgrading the server running the older service pack to the same service pack (or later) that is on the upgraded server. For more information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack. If trusted connections with SQL Server cannot be made using TCP/IP, take the following steps to eliminate the problem: Use the SQL Server Client Network Utility to change the default protocol to named pipes. Use SQL Server Authentication instead of Windows Authentication to migrate the repository. If you cannot resolve the problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
-2147221455   -  Cannot retrieve the repository information from the server computer (<server name>).  MICROSOFT
SQL Server 2000 Analysis Services stores information about the repository in the registry of the computer running the MSSQLServerOLAPServices service. Other applications, such as Analysis Manager or any application using Decision Support Objects (DSO) to perform administrative tasks, must be able to connect to the registry in order to retrieve the repository information. This error typically occurs when the user account attempting to perform an administrative function, using Analysis Manager or a Decision Support Objects (DSO) application, is not a member of either the OLAP Administrators group or the Administrators group.
Ensure that the user account used to connect to the Analysis server has the following permissions: Access to the following registry key on the server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server Connection Info Write permissions on the hidden share, MsOLAPRepository$, which contains the Analysis Services repository and locking files. By default this share is the Bin directory under the Analysis Services directory. Full Control rights on the Bin and Data directories under the Program Files\Microsoft Analysis Services\Bin directory. By default, these folders should allow Everyone full control, but if for security reasons you want to tighten security, ensure that the OLAP Administrators group retains Full Control rights. When you install Analysis Services, a local group named OLAP Administrators is created and given Full Control rights to the preceding registry key and the MsOLAPRepository$ share. Typically, adding the user account to the OLAP Administrators group grants the necessary permissions. If you are unable to resolve this problem, contact your primary support provider.
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
 
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
 
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
 
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
 
 

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