SSAS Error : XML parsing failed at line 1, column 0: A document must contain exactly one root element

when i am planning to redeploy the Cube . I took the latest cube from Production and want to deploy in Dev server . i am getting the fallowing error .


Error 33 XML parsing failed at line 1, column 0: A document must contain exactly one root element. .  0 0

Error 34 Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\E:\MSSQL\Data\DbR4.194.db\MSC ID.112677.dim.xml'.  0 0

Solution : Go the path specified the in the Error on the deploying server not on you local server . and there you will find that file with 0 KB  . Delete that file and redeploy the project .

Comments

  1. AnonymousNovember 21, 2016 at 2:02 PM

    My error is citing a

    > file, '\\?\W:\...'

    but I don't have access to W: in Windows Explorer.

    ReplyDelete
  2. Surendra ThotaNovember 21, 2016 at 10:21 PM

    Search for mentioned file name

    ReplyDelete
  3. LavanyaDecember 14, 2021 at 10:18 PM

    It 's an amazing and awesome blog. Thanks for sharing
    Msbi Developer Course
    Best Msbi Online Training

    ReplyDelete

Post a Comment

Popular posts from this blog

SSAS : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). + Solution

Problem : have installed Analysis service on my server machine through remote login from my service account. I am able to open Analysis services from there. When I open SSMS from the same service account on my local machine, I am not able to connect to that Analysis service. It is giving me error by saying : "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond 10.245.192.111:2382(System)." Solution : Based on my research, the issue was caused by the Browser Service account was changed to the domain account. In your scenario, you can try to connect to the Analysis Service using <Servername>:2383 instead of instance name. Or you can change the Browser Service account to "Local System".
Read more

SSIS Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces

Image
Problem : When we have Multiple Namespaces in the Xml Source which we need to load the Data from   as we shown below Then we will face a issue in generating XSD for that XML Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces. (Microsoft Visual Studio) Solution : First we need to avoid multiple namespaces to transform your source file to a format that doesn’t refer to the namespaces. SSIS has an XML task that can do the transformation. 1) Add the XML task to an SSIS   Control Flow and edit it. 2) Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem. 3) Set the SaveOperationResult property to True and expand the OperationResult branch. Set DestinationType to File Connection and the Destination to a new XML file ( ModifiedInput.XML). 4) Add the below script to a new file and save it with an xslt file extension (Input.XSLT) <
Read more