Showing posts with label deploying. Show all posts
Showing posts with label deploying. Show all posts

Thursday, March 22, 2012

Error Deployiong Analysis Services Cube

Hi:

I am getting the following error when deploying the cube on my laptop.

"The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server."

I confirmed that all the services are running. Can you someone guide me here? This is the first time I am trying to deploy the cube in analysis services 2005. Please let me know.

Thanks

Try using machine name instead of the "localhost". Try connecting to your Analysis Server using SQL Management studio.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

sql

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
BUTTONS:

OK
-

=====================================================
=============================================

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)". (Package Installation Wizard)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found


Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll


regsvr32.exe msxml6.dll



I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
BUTTONS:

OK
-

=====================================================
=============================================

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)". (Package Installation Wizard)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found


Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll


regsvr32.exe msxml6.dll



I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
BUTTONS:

OK
-

=====================================================
=============================================

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)". (Package Installation Wizard)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found


Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll


regsvr32.exe msxml6.dll



I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
BUTTONS:

OK
-

=====================================================
=============================================

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)". (Package Installation Wizard)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found


Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll

I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.
|||

Kapil Aggarwal wrote:

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
BUTTONS:

OK
-

=====================================================
=============================================

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)". (Package Installation Wizard)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.


-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found


Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll

I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.
|||

Kapil Aggarwal wrote:

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

sql

Error deploying report with SQL Server (Visual Studio) 2005

Hi All,
I'm trying to deploy a report that have just been created in Visual
Studio 2005 (for Microsoft CRM) I'm getting an error message
******************************
The project cannot be deployed because no target server is specified.
Provide a value for the TargetServerURL property in the property page
of this project.
******************************
I'm sorry I'm new with this Visual Studio 2005 ... I'm not finding the
place to put the TargetServerURL value in that property page ... The
worst thing is that it is probably right under my nose ... ;-)
Anybody can help a dummy ? ... ThanksProject -> your Project Name Properties (Last Menu Item) on the pop up
window you'll find what you're looking for.
Manny
Frank wrote:
>Hi All,
>I'm trying to deploy a report that have just been created in Visual
>Studio 2005 (for Microsoft CRM) I'm getting an error message
>******************************
>The project cannot be deployed because no target server is specified.
>Provide a value for the TargetServerURL property in the property page
>of this project.
>******************************
>I'm sorry I'm new with this Visual Studio 2005 ... I'm not finding the
>place to put the TargetServerURL value in that property page ... The
>worst thing is that it is probably right under my nose ... ;-)
>Anybody can help a dummy ? ... Thanks
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200701/1

Error Deploying Report

I'm getting a strange error when deploying a report:
Server was unable to process request. --> Could not find file "C:
\WINDOWS\TEMP\7qifavw2.dll".
The strange part is that the dll file name changes each time i try to
deploy. The deploy function was working when I left last night, and
not working first thing this morning. Any idea what's happening here?ugh
I rebooted and it started working again. Strange thing though. I was
trying this from my pc, as well as from the server itself, and got the
same error. Rebooting my pc did not help, but rebooting the server
did. Oh well, now if I had only rebooted a couple hours sooner :-(|||The reason the name of the DLL changes is that this is the compiled result
of some ASP.NET code. I'm surprised that the location is C:\WINDOWS\TEMP --
are you sure? -- but I would expect that location to be different on
different machines and in different OS.
This can happen when something on a site changes and ASP.NET tries to
refresh its compiled code but something interferes with the whole thing
happening correctly. Sometimes it may be a user session that is open and
"pointed" to a particular page on the site.
What I usually do is stop the application in question and clear out *all*
the compiled code for it, so that when the application starts up again
ASP.NET recompiles everything from scratch. I can't be more specific than
that because I really don't know why you would be getting this when
"deploying a report". Which action, exactly, invokes the error on your PC?
>L<
<c-eric.geil@.mci.com> wrote in message
news:1176998968.836336.124600@.e65g2000hsc.googlegroups.com...
> I'm getting a strange error when deploying a report:
> Server was unable to process request. --> Could not find file "C:
> \WINDOWS\TEMP\7qifavw2.dll".
> The strange part is that the dll file name changes each time i try to
> deploy. The deploy function was working when I left last night, and
> not working first thing this morning. Any idea what's happening here?
>

Error deploying managed stored proc

When I try to deploy this managed stored proc assembly on SQL Server 2005 I get this error:

Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x8007000e. You may fix the problem and try again later

I looked on the net but found no documentation about it. I know the CLR v2.0 is working as I have some ASP.NET apps running from this server that use it. Any ideas?

Try the simple code to get a .dll file:

using System.Data;
using System.Data.SqlClient;
using Microsoft.SqlServer.Server;

public partial class StoredProcedures
{
[Microsoft.SqlServer.Server.SqlProcedure()]
public static void SampleSP(string connstring, out int spid)
{
using (SqlConnection conn = new SqlConnection(connstring))
{
conn.Open();

SqlCommand cmd = new SqlCommand("SELECT @.@.SPID", conn);
spid = (System.Int16)cmd.ExecuteScalar();
}
}
}

And then let's manually create assmebly from the dll file in Management Studio:

1. Login to SQL2005 as 'sa', locate a database->new query->execute following command:

alter database yourdb set trustworthy on

go

sp_configure 'clr enabled',1
reconfigure with override

go

2. create an assembly from the dll file

3. create a stored procedure which references the assembly:

create procedure testCLR @.conn nvarchar(max),@.i int output as
external name ClassLibrary2.[StoredProcedures].SampleSP

4. Test the procedure:

declare @.i int

exec testCLR 'Data Source=.;Integrated Security=SSPI;Database=master',@.i output

select @.i

And here is a good torturial for using CLR in SQL2005:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/mandataaccess.asp

Error Deploying Cube

I have just installed Evaluation version of SQL Server 2005. Created a new database with two tables. Created new project with data source pointing to localhost and build a data source view containning tables from database created earlier. After creating the cube, I get following error while deploying the Cube:

OLE DB error: OLE DB or ODBC error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.

Any help!

Regards.

Are you deploying locally or remotely?

Is the user you are trying to deploy as set up in the SQLSERVER2005MSOLAPUser group on the AS server?

|||

It is local and user is member of group you mentioned.

My problem was due to the wrong impersonation information in data source. I have corrected it and now everything is fine.

Thnks.

Error deploying Analysis Service Project

Hi,

We are following the Analysis Service Tutorial and when we tried to deploy we got these errors:

Error 1 OLE DB error: OLE DB or ODBC error: Login failed for user 'PASCAL\CEZAR$'.; 42000. 0 0
Error 2 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 4 Errors in the OLAP storage engine: An error occurred while the 'CalendarYear' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 5 OLE DB error: OLE DB or ODBC error: Login failed for user 'PASCAL\CEZAR$'.; 42000. 0 0
Error 6 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'. 0 0
Error 7 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 8 Errors in the OLAP storage engine: An error occurred while the 'CalendarSemester' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0

We hope someone can help us.

Thanks a lot.

Hi Cezar. Your problem looks like the user PASCAL\CEZAR$ doesn't have access rights to the SQL Server source data, 'Adventure Works DW'. Check the access rights for 'Adventure Works DW' in SQL Server Manager, and verify that the user PASCAL\CEZAR$ has rights to the database.

Hope this helps - Paul Goldy

|||

Hi,

Thanks for your answer. The user error has been solved, but we got other error messages:

Error 1 OLE DB error: OLE DB or ODBC error: SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0
Error 2 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the 'EnglishMonthName' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 4 OLE DB error: OLE DB or ODBC error: SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0
Error 5 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 6 Errors in the OLAP storage engine: An error occurred while the 'CalendarSemester' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 7 Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure. 0 0
Error 8 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 9 Errors in the OLAP storage engine: An error occurred while the 'CalendarYear' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 10 OLE DB error: OLE DB or ODBC error: Opera??o cancelada; HY008. 0 0
Error 11 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 12 Errors in the OLAP storage engine: An error occurred while the 'CalendarQuarter' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0

What can we do?

Yours, Cezar

|||

Hi Cezar. The error you received, "SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0", is saying you do NOT have read permission for the AdventureWorksDW database. In SQL manager 2005 you must manage the permission for the AdventureWorksDW database and allow the user (I assume CEZAR\PASCAL$) db_datareader permission for the database. Here is a link which discusses more about setting permissions for SQL Server:

http://msdn2.microsoft.com/en-us/library/ms189121.aspx

Paul Goldy

error deploying analysis server cube

Has anyone ever received this message before?
"The Description element at line 3123, column 29 (namespace
http://schemas.microsoft.com/analys...ces/2003/engine) cannot appear
under
Envelope/Body/Execute/Command/Batch/Alter/ObjectDefinition/Database/Cubes/Cu
be/Dimensions/Dimension."
All I was doing was adding description to the properties of the dimension
tables. I was doing this so that the report user can see pop-up descriptions
in Report Builder.
I haven't been able to resolve this problem. Not only that - Now that I've
received this error, I haven't been able to reset the solution file so that
I
don't get this error. I have even removed all the description changes I
made, but to no avail.
Can anyone help me?
--JPThere are a couple of things you could try.
1) you could run Profiler while you are trying to deploy, this way you
would be able to capture the XMLA that is being sent to the server. You
would then be able to copy and paste the XMLA into a text editor and
search it. Maybe there is one change that you have missed undoing.
2) If all else fails, you could re-create your project from the database
on the server by starting a new project and choosing the "import
Analysis Services 9.0 database option"
Regards
Darren Gosbell - SQL Server MVP
Blog: http://www.geekswithblogs.net/darrengosbell
In article <16360AA6-10E3-4E75-9124-D939176CC1C2@.microsoft.com>,
Garza_JP@.discussions.microsoft.com says...
> Has anyone ever received this message before?
> "The Description element at line 3123, column 29 (namespace
> http://schemas.microsoft.com/analys...ces/2003/engine) cannot appear
> under
> Envelope/Body/Execute/Command/Batch/Alter/ObjectDefinition/Database/Cubes/
Cube/Dimensions/Dimension."
> All I was doing was adding description to the properties of the dimension
> tables. I was doing this so that the report user can see pop-up descriptio
ns
> in Report Builder.
> I haven't been able to resolve this problem. Not only that - Now that I've
> received this error, I haven't been able to reset the solution file so tha
t I
> don't get this error. I have even removed all the description changes I
> made, but to no avail.
> Can anyone help me?
> --JP
>

Error Deploying An unexpected error occurred while compiling expressions. Native compiler re

When attempting to deploy a series of reports I am receiving the error:

An unexpected error occurred while compiling expressions. Native compiler return value: ‘128’.

The datasources deploy fine, but each report results in the same error. I can build the project and preview each report without issue, it is only on the deploy that the error occurs.

Any help would be appreciated

Jason

just wanted to share the "solution" to the issue.

I attempted to login to the reporting services manager so I could try and upload the reports that way rather than deploying through visual studio and I received an error: Could not find file 'C:\WINDOWS\TEMP\xw1mue_7.dll' The dll changed each time, but I found a post in google groups that suggested restarting the app pool to resolve this issue. Seems to have solved both problems.

I would still like to know why the app pool needed to be restarted....

|||Restart IIS to solve that problem.

Error deploying a CLR Stored Procedure that uses a web service

Ok, first some background.

I am writing my first (complex) CLR Stored Procedure using Visual Studio 2005.

This SP worked fine until I added code to make a web service call. That web service is a wrapper web service I created because the actual web service I need to call uses System. Web.Extensions which was not available in my VS2005 Database Project.

At first I was getting the standard "External Access Assembly" errors, so I created a new user (was using SA) and assigned database ownership to the new user, then assigned permissions to that user. This worked to get it deployed, but I get the following error when its run:

<code>

System.InvalidOperationException: Cannot load dynamically generated serialization assembly. In some hosting environments assembly load functionality is restricted, consider using pre-generated serializer. Please see inner exception for more information. > System.IO.FileLoadException: LoadFrom(), LoadFile(), Load(byte[]) and LoadModule() have been disabled by the host.

System.IO.FileLoadException:

at System.Reflection.Assembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection)

at System.Reflection.Assembly.Load(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence securityEvidence)

at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)

at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)

at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)

at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, S

</code>

Anyone have any ideas?

Thanks!

Dave Borneman

Solution Architect,

anyWare Mobile Solutions.

OK, so when you are using Web services the .NET framework will dynamically generate an assembly based on your proxy code. Dynamic assembly generation is not allowed inside SQL Server (SQLCLR).

What you need to do is to pre-generate the proxy assembly by using the sgen tool and deploy that generated assembly into the database.

Look at this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=74480&SiteID=1 and specifically the 6:th message in that thread how to achieve the pre-generation.

Niels

Monday, March 19, 2012

Error creating Indexes in ROLAP based OLAP in Analysis Server 2005

Hi,

We are implementing OLAP based system in which the team has decided to use ROLAP as storage structure. But we are getting error while deploying the cube. The error is

OLE DB error: OLE DB or ODBC error: Cannot create index on view "Reporting.dbo.Agg_Fact Table_27_48_48_44_44_4" because it references derived table "dbo_Fact_Table" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

It seems that it has created a view that uses derived table and tries to create a clustered index on that. [Indexed View]. The above view definition contains derived table but as we know that the Indexed view can’t contain derived table. What is the workaround for this problem?

Thanks a lot for any advice.

Rakesh Mishra

Hi Rakesh

I got the same problem and can't find any solution. Did you find any workaround to solve the problem

Leo

|||

Hi,

I have experienced the same problem. Has this issue been resolved?

Thanks,

Bill

|||

I am sorry for *bumping* this one up, but I encounter the same problem on my project, so I wonder if there is a solution for it.

I would like to add that my project works well in MOLAP and does process completly without errors, switching to rolap gives the same message as the original poster has, with some different names and numbers for the tables and index columns of course.

Thanks

Ralf

|||

I have encountered this issue as well. I too wonder if there is a solution for this.

It appears to be only an issue when a particular attribute is used in an aggregation.

Error creating Indexes in ROLAP based OLAP in Analysis Server 2005

Hi,

We are implementing OLAP based system in which the team has decided to use ROLAP as storage structure. But we are getting error while deploying the cube. The error is

OLE DB error: OLE DB or ODBC error: Cannot create index on view "Reporting.dbo.Agg_Fact Table_27_48_48_44_44_4" because it references derived table "dbo_Fact_Table" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

It seems that it has created a view that uses derived table and tries to create a clustered index on that. [Indexed View]. The above view definition contains derived table but as we know that the Indexed view can’t contain derived table. What is the workaround for this problem?

Thanks a lot for any advice.

Rakesh Mishra

Hi Rakesh

I got the same problem and can't find any solution. Did you find any workaround to solve the problem

Leo

|||

Hi,

I have experienced the same problem. Has this issue been resolved?

Thanks,

Bill

|||

I am sorry for *bumping* this one up, but I encounter the same problem on my project, so I wonder if there is a solution for it.

I would like to add that my project works well in MOLAP and does process completly without errors, switching to rolap gives the same message as the original poster has, with some different names and numbers for the tables and index columns of course.

Thanks

Ralf

|||

I have encountered this issue as well. I too wonder if there is a solution for this.

It appears to be only an issue when a particular attribute is used in an aggregation.

Error creating Indexes in ROLAP based OLAP in Analysis Server 2005

Hi,

We are implementing OLAP based system in which the team has decided to use ROLAP as storage structure. But we are getting error while deploying the cube. The error is

OLE DB error: OLE DB or ODBC error: Cannot create index on view "Reporting.dbo.Agg_Fact Table_27_48_48_44_44_4" because it references derived table "dbo_Fact_Table" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

It seems that it has created a view that uses derived table and tries to create a clustered index on that. [Indexed View]. The above view definition contains derived table but as we know that the Indexed view can’t contain derived table. What is the workaround for this problem?

Thanks a lot for any advice.

Rakesh Mishra

Hi Rakesh

I got the same problem and can't find any solution. Did you find any workaround to solve the problem

Leo

|||

Hi,

I have experienced the same problem. Has this issue been resolved?

Thanks,

Bill

|||

I am sorry for *bumping* this one up, but I encounter the same problem on my project, so I wonder if there is a solution for it.

I would like to add that my project works well in MOLAP and does process completly without errors, switching to rolap gives the same message as the original poster has, with some different names and numbers for the tables and index columns of course.

Thanks

Ralf

|||

I have encountered this issue as well. I too wonder if there is a solution for this.

It appears to be only an issue when a particular attribute is used in an aggregation.

Error creating Indexes in ROLAP based OLAP in Analysis Server 2005

Hi,

We are implementing OLAP based system in which the team has decided to use ROLAP as storage structure. But we are getting error while deploying the cube. The error is

OLE DB error: OLE DB or ODBC error: Cannot create index on view "Reporting.dbo.Agg_Fact Table_27_48_48_44_44_4" because it references derived table "dbo_Fact_Table" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

It seems that it has created a view that uses derived table and tries to create a clustered index on that. [Indexed View]. The above view definition contains derived table but as we know that the Indexed view can’t contain derived table. What is the workaround for this problem?

Thanks a lot for any advice.

Rakesh Mishra

Hi Rakesh

I got the same problem and can't find any solution. Did you find any workaround to solve the problem

Leo

|||

Hi,

I have experienced the same problem. Has this issue been resolved?

Thanks,

Bill

|||

I am sorry for *bumping* this one up, but I encounter the same problem on my project, so I wonder if there is a solution for it.

I would like to add that my project works well in MOLAP and does process completly without errors, switching to rolap gives the same message as the original poster has, with some different names and numbers for the tables and index columns of course.

Thanks

Ralf

|||

I have encountered this issue as well. I too wonder if there is a solution for this.

It appears to be only an issue when a particular attribute is used in an aggregation.

Friday, February 24, 2012

Error Code = 0x8007000E, External Code = 0x00000000: Exception when deploying the SSAS

Hi
I am getting this error when deploying the Analysis Services Project.

Error Code = 0x8007000E, External Code = 0x00000000:

Can anyone Point me the reason for the same?

Thankyou
Vidya
Test your connection, if it's OK, delete your AS database and deploy it again.

Error Code = 0x8007000E, External Code = 0x00000000: Exception when deploying the SSAS

Hi
I am getting this error when deploying the Analysis Services Project.

Error Code = 0x8007000E, External Code = 0x00000000:

Can anyone Point me the reason for the same?

Thankyou
Vidya
Test your connection, if it's OK, delete your AS database and deploy it again.