Analysis Services Troubleshooting

When a cube or dimension fails to process, verify the following:

• Data source connection strings are correct and the server is reachable.
• All required credentials are stored in the data source.
• No circular dependencies exist between partitions.

Example script to reprocess a cube:

SELECT [DatabaseName] FROM $system.discover_databases;
EXEC Process CubeName WITH ( Update )

High memory usage can cause query timeouts or server restarts.

1. Check vertiport and vertiport_log locations for space.
2. Increase MemoryLimit in msmdsrv.ini if needed.
3. Use XMLA to clear unused caches:

   <ClearCache xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
     <Object>
       <DatabaseID>YourDB</DatabaseID>
     </Object>
   </ClearCache>
   

Typical reasons for security‑related failures:

• Missing role permissions for the object.
• Kerberos constrained delegation not configured.
• Wrong effective user when using ImpersonationInfo.

Sample ImpersonationInfo definition:

<ImpersonationInfo>
  <ImpersonationMode>ImpersonateAccount</ImpersonationMode>
  <Account>DOMAIN\sqlsvc</Account>
  <Password>********</Password>
</ImpersonationInfo>

Check the following when clients cannot connect:

1. Ensure the Analysis Services port (default 2383) is open.
2. Verify the instance is running (services.msc).
3. Confirm the client uses the correct server name and instance.
4. Review the msmdsrv.log for authentication errors.

Common deployment problems and fixes:

Error	Cause	Resolution
0x8004E001	Object already exists	Use ReplaceExisting option or delete the object first.
0xC0202009	Data source connection failed	Update connection string and credentials.