Error running report: date

Showing posts with label date. Show all posts

Monday, March 19, 2012

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:
Phil,
The issue on the post at this site seems to be the same.
http://www.kbalertz.com/Feedback_926629.aspx
The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:
No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:
Phil,
The issue on the post at this site seems to be the same.
http://www.kbalertz.com/Feedback_926629.aspx
The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

SnoChoJoe wrote:
No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Monday, March 12, 2012

Error when changing a group in code

I am getting the following error message when i attempt to set a date field as the group by condition in code.

"The group options for a date, time or date-time condition field must be a date group options object."

Does anyone know what this means or how it can be corrected? Im using VS2005 and ASP.NET

ThanksWell, I'm guessing that you need to provide a valid group option :)
i.e. do you want the dates grouped by day, week, month etc.|||Thanks for your reply. Yes it would seem i would need to set a valid group option but i think firstly for a group field that is using a date/time field the groupOptions property needs to be of type DateTimeGroupOptions. If originally the grouped field was a not date field you can't then change it to a date/time field because the GroupOptions property is Read-Only and can't be changed to the DateTimeGroupOptions object.

error when backing up db using maintenance plan

I am gettnig following error when performing a backup using a maintenance plan:

Date 4/24/2007 11:01:23 AM
Log Job History (MaintenancePlan1.Subplan_1)

Step ID 1
Server 006-DEVSQL2005
Job Name MaintenancePlan1.Subplan_1
Step Name Subplan_1
Duration 00:00:09
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: tcs\svcDBASQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:01:24 AM. The return value was unknown. The process exit code was -1073741819. The step failed.

I am able to use the transact sql generated by the maint plan and create a backup. is this a 64 bit issue?

HI Shahab,

Check for the error in the error log and let us know. It should be logged in the error log at the time your backup failed.

Jag

Friday, February 24, 2012

Error trying to save a date field

Hi there, right now i'm working with a VB6 project that connects to a
SQLSERVER 2000.
I discovered a problem that, i hope you can help me.
The problem is that, when i try to save a record with a date field - the
date saved in database is 2 days more that the typed date. ALWAYS 2 DAYS!!!
Don't know why.
In order to save a record to DB i try to use val = cdec(val), where val is a
date value, and for strings values i just use val = "'" & val & "'", and so
on... for diferent types of fields.
Because i'm developing for a spanish environment i decided to convert dates
in the right format ("dd/mm/yyyy") and try to have regional settings that
match national language and location.
If anybody can help me, please i will appreciate it.
Felix.You probably represent the date as some umber datatype (float, int or so) an
d the VB "base date"
differs from the SQL Server "base date" by 2 days. Never use numbers to repr
esent datetime in SQL,
represent them as strings. Or better yet, use a date datatype in your host l
anguage and use
parametized queries. Read here about datetime datatype in SQL Server:
http://www.karaszi.com/SQLServer/info_datetime.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Felix Quevedo C." <FelixQuevedoC@.discussions.microsoft.com> wrote in messag
e
news:3FBFD807-414F-4846-9DCE-A90AAFF1CB95@.microsoft.com...
> Hi there, right now i'm working with a VB6 project that connects to a
> SQLSERVER 2000.
> I discovered a problem that, i hope you can help me.
> The problem is that, when i try to save a record with a date field - the
> date saved in database is 2 days more that the typed date. ALWAYS 2 DAYS!!
!
> Don't know why.
> In order to save a record to DB i try to use val = cdec(val), where val is
a
> date value, and for strings values i just use val = "'" & val & "'", and s
o
> on... for diferent types of fields.
> Because i'm developing for a spanish environment i decided to convert date
s
> in the right format ("dd/mm/yyyy") and try to have regional settings that
> match national language and location.
> If anybody can help me, please i will appreciate it.
> Felix.|||Sounds like VB is converting the date to an integer and back again, and
using its own base date (1899-12-30) instead of SQL Server's (1900-01-01).
Try taking the literal string and passing it as a string. If you do this,
be sure to type in a proper format, e.g. YYYYMMDD. If you type in
mm/dd/yyyy there are several points along the way where this can easily
convert to dd/mm/yyyy.
A
"Felix Quevedo C." <FelixQuevedoC@.discussions.microsoft.com> wrote in
message news:3FBFD807-414F-4846-9DCE-A90AAFF1CB95@.microsoft.com...
> Hi there, right now i'm working with a VB6 project that connects to a
> SQLSERVER 2000.
> I discovered a problem that, i hope you can help me.
> The problem is that, when i try to save a record with a date field - the
> date saved in database is 2 days more that the typed date. ALWAYS 2
> DAYS!!!
> Don't know why.
> In order to save a record to DB i try to use val = cdec(val), where val is
> a
> date value, and for strings values i just use val = "'" & val & "'", and
> so
> on... for diferent types of fields.
> Because i'm developing for a spanish environment i decided to convert
> dates
> in the right format ("dd/mm/yyyy") and try to have regional settings that
> match national language and location.
> If anybody can help me, please i will appreciate it.
> Felix.|||thanks a lot Tibor. My problem is solved - Felix.
"Tibor Karaszi" wrote:

> You probably represent the date as some umber datatype (float, int or so)
and the VB "base date"
> differs from the SQL Server "base date" by 2 days. Never use numbers to re
present datetime in SQL,
> represent them as strings. Or better yet, use a date datatype in your host
language and use
> parametized queries. Read here about datetime datatype in SQL Server:
> http://www.karaszi.com/SQLServer/info_datetime.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Felix Quevedo C." <FelixQuevedoC@.discussions.microsoft.com> wrote in mess
age
> news:3FBFD807-414F-4846-9DCE-A90AAFF1CB95@.microsoft.com...
>

Sunday, February 19, 2012

Error that has nothing to do with my cube

I right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

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.

Edward Melomed (MSFT)

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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 right click on my AS cube and click "Process". It tells me the server content is out of date would I like to build and deploy first. i say yes.

I get this error

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.

Edward Melomed (MSFT)

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.

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.

|||

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:

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.

Friday, February 17, 2012

Error Sorting

I need the results of a view sorted by date. When the order by date is added
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
Thanks
Niles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com
|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:

> Niles wrote:
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
David Gugick
Imceda Software
www.imceda.com
|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is added
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maximum
> of 8094"
> Is there a way around this?
> Thanks

Error Sorting

I need the results of a view sorted by date. When the order by date is adde
d
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
ThanksNiles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:

> Niles wrote:
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
David Gugick
Imceda Software
www.imceda.com|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is add
ed
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maxim
um
> of 8094"
> Is there a way around this?
> Thanks

Error Sorting

I need the results of a view sorted by date. When the order by date is added
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
ThanksNiles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:
> Niles wrote:
> > I need the results of a view sorted by date. When the order by date
> > is added to the view I get the following error from SQL/ODBC SQL
> > Driver: "cannot sort a row of size 8813, which is greater than the
> > allowable maximum of 8094"
> > Is there a way around this?
> >
> > Thanks
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
--
David Gugick
Imceda Software
www.imceda.com|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is added
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maximum
> of 8094"
> Is there a way around this?
> Thanks

Monday, March 19, 2012

Error when connecting to SSIS.

Error when connecting to SSIS.

Monday, March 12, 2012

Error when changing a group in code

error when backing up db using maintenance plan

Friday, February 24, 2012

Error trying to save a date field

Sunday, February 19, 2012

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Error that has nothing to do with my cube

Friday, February 17, 2012

Error Sorting

Error Sorting

Error Sorting

Error running report

Blog Archive

About Me