Error accessing report: save

Showing posts with label save. Show all posts

Thursday, March 22, 2012

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.

-
BUTTONS:

OK
-

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

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

-
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)

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

-
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:

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
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

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

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

-
Program Location:

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

-
Program Location:

Ashwani Sharma has the following solution:

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 am also receiving this error:

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

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

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

No description found

Program Location:

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

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.

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
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

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

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

-
Program Location:

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

-
Program Location:

Ashwani Sharma has the following solution:

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 am also receiving this error:

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

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

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

No description found

Program Location:

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

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.

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
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

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

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

-
Program Location:

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

-
Program Location:

Ashwani Sharma has the following solution:

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 am also receiving this error:

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

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

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

No description found

Program Location:

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.

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
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

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

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

-
Program Location:

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

-
Program Location:

Ashwani Sharma has the following solution:

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 am also receiving this error:

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

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

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

No description found

Program Location:

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:

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.

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

Sunday, March 11, 2012

'Error converting data type varchar to int' : Solution

Here is the solution to this error message if anyone gets one in the future...It took me about two days to figure out.

This error occurs if you save your stored procedure before execute it. Always execute first before you save. If you save before executing, the server will store its own defaults, usually integers.

This error aslo occurs if your datatypes do not match when passing values from code into the variables of a stored procedure.

It also occurs if the datatypes in your sql file do not match those of the original stored procedure.

You can check to see if the file saved in the "Projects" folder matches with the original by doing the following:

Expand Database, Expand Programmability, Expand Stored Procedures, Expand (Your Stored Procedure), Expand Parameters. Read the datatypes that are revealed in the tree.

Then go to File>Open>Projects>(save sql file). Click open.

View the datatypes in the file. If the datatypes in the file do not match the datatypes in the tree, what you must do to correct, as one solution, is delete both the file and stored procedure.

Then create a new stored procedure by right clicking the stored procedure node. Rewrite the store procedure, execute and then save. Everything should be okay.

Hi,

Thanks that you come back to the forums and want to give something of your solution to your actual problem back.

But I don′t know what your actual problem was (as you did not mentioned it clearly). Perhaps we could summarize this a bit more like Problem: xxxx, Solution: xxx. But from the information given I cannot tell what your actual problem was. I can′t even see why you do all the saves and deletes :-) ?

Jens K. Suessmeyer.

-
http://www.sqlserver2005.de
-

Friday, February 24, 2012

error changing subscription properties

Made a change to the publisher security parameters, tried to save and got the following message:

"An error occurred saving the changes to the subscription.

Additional information.

"Value" is longer than 128 that it should not exceed.
Parameter name: value (Microsoft.sqlserver.rmo)

Doesn't make much sense to me.
Tried to change it back and all I get is this error (i had set the userid to domain/userid which was obviously an error).Hi, Bruce

Would you like provide more repro steps? And which version of SQL server are you using?

BTW, did you really input authentication login/password which is londer than 128 characters or any change will cause this error?

Also, when you tried to change back, were you stucked with this error or you succeeded in changing back.

Thanks
Yunjing|||

SQL 2005 standard - current release version

No it wasn't longer than 128

I'm stuck with it - I can't change it back....

Steps:
a) Well I had a 2005 subscription which was working fine (anonymous merge over HTTPS)
b) I made the mistake of changing the subscription properties-> publisher connection -> Use sql server authentication-> Login to domain\userid
c) pressed ok + ok - then got that error

Thanks

Bruce

|||

Hi, Bruce

Thanks for the info you provided.

I tried with 2005 anonymous merge pull sub with sync through web. But I couldn't reproduce the problem by following the steps you showed. I also read the product related source code and didn't find any code work different for changing login no matter for standard or enterprise SKU.

Did you change other sub properties value besides this login? Could you check if the issue was caused by other changes?

Thanks a lot

Yunjing

|||

It's a bit hard now to provide further info - I'm pretty sure it was the only thing I changed at the time....

thanks for your help anyway - this is a great service....
Bruce

|||

Thanks for all info you provided. If I can reproduce the issue in the future, I will let you know as well.

-Yunjing

error changing subscription properties

Made a change to the publisher security parameters, tried to save and got the following message:

"An error occurred saving the changes to the subscription.

Additional information.

"Value" is longer than 128 that it should not exceed.
Parameter name: value (Microsoft.sqlserver.rmo)

Doesn't make much sense to me.
Tried to change it back and all I get is this error (i had set the userid to domain/userid which was obviously an error).

Hi, Bruce

Would you like provide more repro steps? And which version of SQL server are you using?

BTW, did you really input authentication login/password which is londer than 128 characters or any change will cause this error?

Also, when you tried to change back, were you stucked with this error or you succeeded in changing back.

Thanks
Yunjing|||

SQL 2005 standard - current release version

No it wasn't longer than 128

I'm stuck with it - I can't change it back....

Thanks

Bruce

|||

Hi, Bruce

Thanks for the info you provided.

Did you change other sub properties value besides this login? Could you check if the issue was caused by other changes?

Thanks a lot

Yunjing

|||

It's a bit hard now to provide further info - I'm pretty sure it was the only thing I changed at the time....

thanks for your help anyway - this is a great service....
Bruce

|||

Thanks for all info you provided. If I can reproduce the issue in the future, I will let you know as well.

-Yunjing

Thursday, March 22, 2012

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Sunday, March 11, 2012

'Error converting data type varchar to int' : Solution

Friday, February 24, 2012

error changing subscription properties

error changing subscription properties

Error accessing report

Blog Archive

About Me