Database Synchronization IN Analysis Services - the story goes on
Hi,
I am getting errors while synchronizing databases between two machines in my LAN using the SQL server 2005 Management Studio – analysis services’ synchronize option. After the XMLA script generated by deployment wizard from my cube was executed successfully. I kept my system as the Development server and the other system as the Production server. Then in the Production server’s SQL server 2005 Management Studio – analysis services’ synchronize option I gave source server name as mine and source database as the cube filename. Then executed the synchronize command and the errors appeared ("peer prematurely closed the connection”; “error was encountered in the transport layer"). What is the reason for this?
REsult obtained when Executed:
<return xmlns="urn:schemas-microsoft-com:xml-analysis">
<results xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
<root xmlns="urn:schemas-microsoft-com:xml-analysis:empty" />
<root xmlns="urn:schemas-microsoft-com:xml-analysis:empty" />
</results>
</return>
Thanks,
Somu
Install SP1 on both servers and see if the same behavior is happening again.
If the problem persists, please contact Microsoft Customer Support Services.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Try deleting database on the target server and run synchronization again. But beyond that there is nothing more to suggest. The situation looks like a bug in a product and you should contact Customer Support Services to get it looked at.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
I was experiencing the same problem. I tried deleting the database on the target server and then rerunning synchronization. But that also failed with the same error. Then I recreated the database (empty database) on the target server. When I ran synchronization again, it succeeded. Thus, the procedure appears to be:
1. Generate synchronization script.
2. Delete the database on target server if it exists.
3. Recreate the database on target server.
4. Run the synchronization script.
The fact of having to delete the database obviously defeats the purpose of the synchronize database command which is to refresh the data transparent to the end users. Hopefully, there is a "solution" to this problem.
Hello everybody.
At the present we experience the same problem - when trying to synchronize databases on two different servers using Management Studio. I tried to follow the steps described in the previous post - with DB re-creation - but it did not bring anything. When I try to run the XMLA script to synchronize my newly created (empty) DB with the source one, I still get the same error - "Error on the transpor layer...".
Does anyone found any solution for the problem?
Regards,
Andrey.
Hello again.
I made several tests using SQL Profiler, and noticed the following: the synchronization - ran as XMLA script or directly using menu command - connects to the source datbase using anonymous logon. And is being rejected. Perhaps, this might be the reason for the error at the transport layer.
Regards,
Andrey.
Hi again.
Here is another thread with the same issue: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=560221&SiteID=17
Does anyone know the solution? How can we overcome this problem with ANONYMOUS LOGON?
Regards,
A.
