Tuesday, March 27, 2012
Error when SQL 2000 start
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-01-20 11:05:36.59 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-01-20 11:05:36.59 server All rights reserved.
2004-01-20 11:05:36.59 server Server Process ID is 115.
2004-01-20 11:05:36.59 server Logging SQL Server messages in file 'C:\MSSQL7\log\ERRORLOG'.
2004-01-20 11:05:36.63 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-01-20 11:05:36.66 server SQL Server configured for thread mode processing.
2004-01-20 11:05:36.66 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-01-20 11:05:36.67 server Attempting to initialize Distributed Transaction Coordinator.
2004-01-20 11:05:38.69 spid3 Starting up database 'master'.
2004-01-20 11:05:38.85 spid3 Server name is 'DB_SERVER'.
2004-01-20 11:05:38.85 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-01-20 11:05:38.87 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-01-20 11:05:38.87 server SQL server listening on 192.168.1.29:1433, 172.16.48.10:1433, 127.0.0.1:1433.
2004-01-20 11:05:38.87 server SQL Server is ready for client connections
2004-01-20 11:05:38.87 spid5 Starting up database 'model'.
2004-01-20 11:05:38.87 spid8 Starting up database 'msdb'.
2004-01-20 11:05:38.87 spid9 Starting up database 'pubs'.
2004-01-20 11:05:38.87 spid10 Starting up database 'Northwind'.
2004-01-20 11:05:38.87 spid11 Starting up database 'SIM'.
2004-01-20 11:05:39.21 spid5 Error: 9003, Severity: 20, State: 1
2004-01-20 11:05:39.21 spid5 The LSN (5:377:1) passed to log scan in database 'model' is invalid..
2004-01-20 11:05:39.31 spid8 Bypassing recovery for database 'msdb' because it is marked SUSPECT.
2004-01-20 11:05:39.39 spid11 Starting up database 'GMS'.
2004-01-20 11:05:39.39 spid8 Starting up database 'euro'.
2004-01-20 11:05:40.14 spid10 Starting up database 'TigrisDB'.have you moved your system's devices around recently?|||Originally posted by ms_sql_dba
have you moved your system's devices around recently?
No, but 2 weeks before, I receive a message (Administrator alert) from PC with installed on SQL 2000.
"Drive Z: is nearly full. 1216688128 bytes are available.
Please warn users and delete unneeded files."
On "drive Z:" there is 9GB free space ...
Thanks for reading.
Best Regards|||looks like your system databases is having some problem.
try restarting sql server in single user mode and do a dbcc checkdb on model and msdb.
If this do not work, you might have to rebuild them
amit
Monday, March 19, 2012
Error when deploying a report
I hope someone can help. I'm new to reporting services 2005, and I'm currently going through Microsoft's tutorial.
I can build a report no problem. But when it comes to deploying the report to a web page, the following message appears:
Build started: Project: Reporting Services Tutorial, Configuration: Production
Build complete -- 0 errors, 0 warnings
Deploy started: Project: Reporting Services Tutorial, Configuration: Production
Deploying to http://localhost/reportserver
Error : Response is not well-formed XML.
Deploy complete -- 1 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
This "reponse is not well-formed XML" error also occurs when I try to expand any of the folders from a "reporting services" server type in management studio.
Any ideas would be greatly appreciated!
Cheers
Richard Powell
are you able to view the xml of the report in Visual Studio?(right click on the file in solution explorer and select 'view code')
at least this will confirm that the report is well formed.
have you managed to corrupt the css for report manager?
I can but empathise, i'm getting mighty sick of this product..|||
Hello Adolf
I am able to view the XML code after choosing "view code" in solution explorer.
What do you mean by a css in report manager? I did say I was new to this.
Richard
|||For future reference, I have got this working now. When deploying the same report another time, a different error message appeared. Which was something like "The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server".
To stop this appearing, run "reporting services configuration" and connect to the appropriate server. Then click on "encryption keys" and click on the delete button that is under "delete encrypted content". After doing that, I am now able to deploy reports.
Error when deploying a report
I hope someone can help. I'm new to reporting services 2005, and I'm currently going through Microsoft's tutorial.
I can build a report no problem. But when it comes to deploying the report to a web page, the following message appears:
Build started: Project: Reporting Services Tutorial, Configuration: Production
Build complete -- 0 errors, 0 warnings
Deploy started: Project: Reporting Services Tutorial, Configuration: Production
Deploying to http://localhost/reportserver
Error : Response is not well-formed XML.
Deploy complete -- 1 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
This "reponse is not well-formed XML" error also occurs when I try to expand any of the folders from a "reporting services" server type in management studio.
Any ideas would be greatly appreciated!
Cheers
Richard Powell
are you able to view the xml of the report in Visual Studio?(right click on the file in solution explorer and select 'view code')
at least this will confirm that the report is well formed.
have you managed to corrupt the css for report manager?
I can but empathise, i'm getting mighty sick of this product..|||
Hello Adolf
I am able to view the XML code after choosing "view code" in solution explorer.
What do you mean by a css in report manager? I did say I was new to this.
Richard
|||For future reference, I have got this working now. When deploying the same report another time, a different error message appeared. Which was something like "The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server".
To stop this appearing, run "reporting services configuration" and connect to the appropriate server. Then click on "encryption keys" and click on the delete button that is under "delete encrypted content". After doing that, I am now able to deploy reports.
Friday, February 24, 2012
Error trying to build and deploy for first time
I'm getting a timeout error when trying to deploy my SSAS project for the first time - any suggestions on where to go from here?
Error 1 OLE DB error: OLE DB or ODBC error: Query timeout expired; HYT00. 0 0
Error 2 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Property Address', Name of 'Property Address' was being processed. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the 'Unit Number' attribute of the 'Property Address' dimension from the 'foo' database was being processed. 0 0
Error 4 Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure. 0 0
Error 5 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Property', Name of 'Property' was being processed. 0 0
Error 6 Errors in the OLAP storage engine: An error occurred while the 'Status Type ID' attribute of the 'Property' dimension from the 'foo' database was being processed. 0 0
How long time does the task take until you see the timeout error? Also, could you check network connectivity to the relational datasource? What authentication do you use?
Sunday, February 19, 2012
Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
|||We had this same problem. As soon as we upgraded the target machine to SP2, the problem went away.Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
|||We had this same problem. As soon as we upgraded the target machine to SP2, the problem went away.Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
|||We had this same problem. As soon as we upgraded the target machine to SP2, the problem went away.Error that has nothing to do with my cube
I get this error
Error 1 File system error: The following file is corrupted: Physical file: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.0.dim\1.Start Date.(All).sstore. Logical file . Errors in the metadata manager. An error occurred when loading the Product dimension, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Dim Product.1.dim.xml'. Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\E:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
This file has nothing to do with my database/project and is not even in the solution. Why is my deploy getting failed due to this file?
AllanDear Allan,
I have same problems, anybody out there with an solution?
Regards
Michael|||Michael
Hast du etwas fruher getan? Ich hatte das AS beispiel Projekt aber in eine verschiedene loesung eingesetzt. Vielleich gibt's etwas kaputt?
Have you done anything earlier? I had deployed the sample AS project but in a different solution. Perhaps there is something broken?
Allan
|||Allan,
I added befor a second fact table, but even when I deleted the second one I can no longer deploy the solution.
Michael|||Try to clean up your data directory and re-deploy your solution.
You data directory by default is under C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\Data.
It would be also very helpful if you can post exact steps leading to the situation you describe.
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Edward.
Besides my data Directory for OLAP being in MSSQL.2 this works. i had already done this in fact. What I would like to hear though is why this happens.
Why does this happen?
Any way to stop it from happening again?
Thanks for anything you can offer.
Allan|||
One of the files in the data folder got corrupted and the error you are seeing indicates that Analysis Server was unable to load it.
Now, about how did that happen: the hope is that you would provide series of steps on how did you get in such situation :)
We are looking into every instance of such corruption, it usually indicates bug in the product, and in order to fix the problem we need to be able to reproduce it.
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm getting this same error, have cleaned up my data directory, and still it is not resolved. Any other ideas?
|||
Hi,
I am getting the same error. I will try to give as much info regarding this issue as possible. Hopefully it will help.
Since I am new to Analysis, I was practicing with the BI tool by setting up different dsvs, cubes, mining structures, etc. Most of them through the wizard. Every time I reached a level that I knew I was basically wrong and things were not working I would delete the previously generated output from the wizard. I started noticing this error, after I had deleted a two mining structures (outputs of wizard), followed by deleting I believe the dimensions first and then the cube (all related). I was working on another dsv and setting up the dimension and fact tables and everything seemed fine, I generated the cube fine as well. But processing the new cube results in this error. At the time I was working in the same soln. I started a new soln -> same error. Reregistered msolap90.dll same error. deleted the xml that seemed to be causing the problem and seemed to be corrupt (I did find it in the path specified) -> still the same error. Seems like I am stuck and can't do anything any more with analysis services. I was hoping that there was a soln for this problem online, but I guess short of reinstalling there is none.
If there is anything I would love to know, thanks,
Amadelle
|||I had similar errors but they referred to the correct project but said they could not find a certail dim.xml file.
I refreshed the data source views
I right clicked the database and selected validate database. That seemed to clean up the problem.
the error has reoccurred when I try to process the cube, which has a legitmate error (missing filed).
However, the dimensions can no longer be processed.
"file system error. The following error occurred during a file operation. The system cannot find the file specified. \\?\C:Program files\Microsoft Sql Server\MSSQL.2\OLAP\Data\Touch.45.db\Project4447005.dim.xml"
|||I had a similar problem.
1. I restored a database from an .abf file. The database was now visible in SQL Server Management Studio.
2. I was unable to browse or view properties for any cube, not just the cubes in the restored database. I was also unable to delete the restored database.
3. I stopped the Analysis Services service (not sure whether this was necessary)
4. I deleted the folder in my data directory (under mssql.2) corresponding to the restored .abf
5. I re-started the service
6. I was able to surf my other cubes
7. I was also able to delete the folder in Analysis Services for the corrupt database.
I'm piling on to an old post. Has this been fixed yet?
|||I have a similar problem, and I could not fix it by deleting the folder in data directory and restarting the service.
I have AS database witch works on my computer. When I tried to restore it on another computer I received:
"Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\BudOlap07.45.db\Act List1.16.dim.xml"
I’ve deleted the folder in data directory and restart the service, but I could not still use it.
I didn’t see no cubes and dimensions in it.
I appreciate any help!
|||We had this same problem. As soon as we upgraded the target machine to SP2, the problem went away.