I am using the analysis services synchronization command to sync two
SSAS databases, and i am able to finish first synchronization
successfully. Then i add some more data to source cube (process source
server db) and run the sync command again. It does perform the copy to
the target server, and when it comes to switch the folder names, it
stops the SSAS service on the target server and command fails. Any
insight or help is greatly appreciated.

Following are the steps/observations:

Environment:
Both source and target servers: SQL Server Analysis Service 2008 SP1,
Windows 2003 Server, 64 Bit.
SSAS DB Size (Processing (Source) Server): Initial Size 135 GB .
Space available (SAN Drive) 150 GB
SSAS DB Size (Processing (Source) Server): After processing 145 GB .
Space available (SAN Drive) 140 GB
SSAS DB Size (Target Server): Initial Size 135 GB (After first
succesful sync). Space available (SAN Drive) 460 GB

Command Used:
<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.4;Data
Source=SRC_SVR;ConnectTo=10.0;Integrated Security=SSPI;Initial
Catalog=DB_NAME</ConnectionString>
<Object>
<DatabaseID>DB_NAME</DatabaseID>
</Object>
</Source>
<SynchronizeSecurity>CopyAll</SynchronizeSecurity>
<ApplyCompression>true</ApplyCompression>
</Synchronize>

- First Execution Succeeds
- Process more data on source server
- Run the above command
- Observe data folder on target server, it creates a temp folder and
eventually names it as DB_NAME.1.DB folder. The service stops and
query ends with following error:

Connection either timed out or was lost
Execution Complete

- More obersation on data folder, after service is stopped: DB_NAME.
0.DB is 135 GB in size, DB_NAME.1.DB is about 20 GB in size and
conatains the data for partitions processed after first
syncronization.

- Service starts automatically after a few minutes (although no
recovery is set for service).

- The database on traget server still shows the old data.

- Extract from msmdsrv log file on target server:

(12/13/2010 2:23:46 PM) Message: Errors in the metadata manager. An
error occurred when loading the XYZ cube, from the file, '\\?\E:\OLAP
\Data\DB_NAME.1.db\CUBENAME.6.cub.xml'. (Source: \\?\c:\Program Files
\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log\msmdsrv.log, Type:
3, Category: 289, Event ID: 0xC1210013)
(12/13/2010 2:23:46 PM) Message: (Source: \\?\c:\Program Files
\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log\msmdsrv.log, Type:
3, Category: 256, Event ID: 0xC1000016)
(12/13/2010 2:35:25 PM) Message: Errors in the metadata manager. An
error occurred when instantiating a metadata object from the file, '\\?
\E:\OLAP\Data\DB_NAME.1.db.xml'. (Source: \\?\c:\Program Files
\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log\msmdsrv.log, Type:
3, Category: 289, Event ID: 0xC1210012)
(12/13/2010 2:35:35 PM) Message: The flight recorder was started.
(Source: \\?\c:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER
\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)
(12/13/2010 2:35:35 PM) Message: Service started. (Source: \\?\c:
\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)

Hi we have exactly the same problem, any solutions?

Thank You

On 13 Dic, 21:53, Sameer <sameerda... (AT) gmail (DOT) com> wrote: