January 7, 2019 at 6:06 pm
Hi,
Happy New Year!
I am having intermittent errors in the job step which synchronizes SSAS database:
The operation has been cancelled because there is not enough memory available for the application. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine.Backup and restore errors: An error occurred while synchronizing the "XYZ" database.
I have 3 servers involved:
Server1 (Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64)) - the SQL server on which job is run and the one I get the above error on.
Server2 (Analysis Services 13.0.4466.4) the source server from which the database is synchronized from.
Server3 (Analysis Services 13.0.4466.4) the destination server to which the database is synchronized to.
The command (type is SQL Server Analysis Services Command) which is run by the job step is the following:
<Synchronize xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Source>
<ConnectionString>Provider=MSOLAP.6;Data Source=Server3;Integrated Security=SSPI;Initial Catalog=MyDatabase;Connect Timeout=600</ConnectionString>
<Object>
<DatabaseID>MyDatabase</DatabaseID>
</Object>
</Source>
<SynchronizeSecurity>CopyAll</SynchronizeSecurity>
<ApplyCompression>true</ApplyCompression>
</Synchronize>
Which server is actually having the memory issue: the SQL Server with the job, the source or the destination server?
How can I fix this error?
Thanks.
January 7, 2019 at 7:23 pm
Roust_m - Monday, January 7, 2019 6:06 PMHi,Happy New Year!
I am having intermittent errors in the job step which synchronizes SSAS database:
The operation has been cancelled because there is not enough memory available for the application. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine.Backup and restore errors: An error occurred while synchronizing the "XYZ" database.I have 3 servers involved:
Server1 (Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64)) - the SQL server on which job is run and the one I get the above error on.
Server2 (Analysis Services 13.0.4466.4) the source server from which the database is synchronized from.
Server3 (Analysis Services 13.0.4466.4) the destination server to which the database is synchronized to.The command (type is SQL Server Analysis Services Command) which is run by the job step is the following:
<Synchronize xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Source>
<ConnectionString>Provider=MSOLAP.6;Data Source=Server3;Integrated Security=SSPI;Initial Catalog=MyDatabase;Connect Timeout=600</ConnectionString>
<Object>
<DatabaseID>MyDatabase</DatabaseID>
</Object>
</Source>
<SynchronizeSecurity>CopyAll</SynchronizeSecurity>
<ApplyCompression>true</ApplyCompression>
</Synchronize>Which server is actually having the memory issue: the SQL Server with the job, the source or the destination server?
How can I fix this error?Thanks.
My guess would be the source but you should be able to find it in the servers SSAS log, MSMDSRV.log. You may have some other information in the log as well.
It could be a shortage of memory but often the error is more related to having memory misconfigured for Analysis Services - you would want to check those settings first.
Memory Properties
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply