Error accessing report: package

Showing posts with label package. Show all posts

Thursday, March 29, 2012

Error executing xp_cmdshell from within a SQL task in a DTS package...

Hello

I am trying to execute xp_cmdshell' from within a DTS package that
was created by another person. When I try to execute that SQL Task'
selectively from within the package, I get the following error
message:

Error Title: Package Error
Error Details:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: xpsql.cpp: Error 87 from GetProxyAccount on line
604

Why is this error message popping up? When I create a new package
(myself) and create an exact same SQL task as above and run it, the
SQL task runs fine.

Appreciate any help / feedback.

Thanks in Advance
Jagannathan SanthanamWhen a sysadmin role member executes xp_cmdshell, it runs under the
security context of the SQL Server service account. However, when a
non-sysadmin user executes the proc, it runs under the SQL Agent proxy
account.

It looks like there is an issue with your configuration of the proxy
account and/or SQL Server service account security. Enterprise Manager
automatically assigns the necessary rights to these accounts when these
are specified or changed via the GUI. Alternatively, you can manually
assign the following Windows rights to the accounts.

<Excerpt
href="http://support.microsoft.com/default.aspx?scid=kb;en-us;264155"
MSSQLServer and SQLServerAgent Services
- Act as part of the Operating System.
- Increase Quotas.
- Replace a process level token.
- Log on as a batch job.
SQLAgentCmdExec Account
- Log on as a batch job.

NOTE: You must restart the entire server, not just the SQL Services, in
order for any changes made to user rights permissions to take effect.

</Excerpt
--
Hope this helps.

Dan Guzman
SQL Server MVP

--------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index...epartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--------

"Jagannathan Santhanam" <jags_32@.yahoo.com> wrote in message
news:605df08e.0311170307.39d9b1f1@.posting.google.c om...
> Hello
> I am trying to execute 'xp_cmdshell' from within a DTS package that
> was created by another person. When I try to execute that 'SQL Task'
> selectively from within the package, I get the following error
> message:
> Error Title: Package Error
> Error Details:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: xpsql.cpp: Error 87 from GetProxyAccount on line
> 604
>
> Why is this error message popping up? When I create a new package
> (myself) and create an exact same SQL task as above and run it, the
> SQL task runs fine.
> Appreciate any help / feedback.
> Thanks in Advance
> Jagannathan Santhanam

Error executing SSIS package

Hello,
I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
created several SSIS packages and run them under proxy account. At first
they worked just fine, but then all of them started to fail with the error
messages like this one:
Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
NonTransactableSql Execute SQL Task Description: An error occurred with
the following error message: "Could not find file 'I:\Users\Peter
Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
step failed.
If the cause is really in this tmp file, it doesn't make any sense. Yes, I'm
deleting my tmp files periodically, so I don't have these files. It's hard
to believe that SQL Server relies on tmp files that are often deleted. Plus,
I was running the same packages on Windows XP for over a year and never had
problems like this.
What else could it be and how to fix it? Is it a security issue?
I would appreciate your suggestions very much.
Thank you,
--
Peter AfoninHi Peter
"Peter Afonin" wrote:
> Hello,
> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
> created several SSIS packages and run them under proxy account. At first
> they worked just fine, but then all of them started to fail with the error
> messages like this one:
> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
> NonTransactableSql Execute SQL Task Description: An error occurred with
> the following error message: "Could not find file 'I:\Users\Peter
> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
> step failed.
> If the cause is really in this tmp file, it doesn't make any sense. Yes, I'm
> deleting my tmp files periodically, so I don't have these files. It's hard
> to believe that SQL Server relies on tmp files that are often deleted. Plus,
> I was running the same packages on Windows XP for over a year and never had
> problems like this.
> What else could it be and how to fix it? Is it a security issue?
> I would appreciate your suggestions very much.
> Thank you,
> --
> Peter Afonin
>
I would suspect that the issue is probably with 'I:\Users\Peter
Afonin\AppData\Local\Temp' not existing where is your temp directory set to?
John|||Hi John,
No, this directory is real. This is a default directory in Vista (I have it
on partition I).
Thank you,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6899EAEE-6306-4D47-913B-BF503C445D66@.microsoft.com...
> Hi Peter
> "Peter Afonin" wrote:
>> Hello,
>> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
>> created several SSIS packages and run them under proxy account. At first
>> they worked just fine, but then all of them started to fail with the
>> error
>> messages like this one:
>> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
>> NonTransactableSql Execute SQL Task Description: An error occurred
>> with
>> the following error message: "Could not find file 'I:\Users\Peter
>> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
>> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
>> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
>> step failed.
>> If the cause is really in this tmp file, it doesn't make any sense. Yes,
>> I'm
>> deleting my tmp files periodically, so I don't have these files. It's
>> hard
>> to believe that SQL Server relies on tmp files that are often deleted.
>> Plus,
>> I was running the same packages on Windows XP for over a year and never
>> had
>> problems like this.
>> What else could it be and how to fix it? Is it a security issue?
>> I would appreciate your suggestions very much.
>> Thank you,
>> --
>> Peter Afonin
> I would suspect that the issue is probably with 'I:\Users\Peter
> Afonin\AppData\Local\Temp' not existing where is your temp directory set
> to?
> John|||John, I can confirm that SQL Server is indeed looking for these tmp files.
1. I've recreated my packages, they worked fine.
2. I removed all files from I:\Users\Peter Afonin\AppData\Local\Temp folder.
The packages stopped working, giving me the error I mentioned before.
3. I put these tmp files back to this folder, the packages work fine again.
This is something that I've never heard before and that doesn't make any
sense. Why this never happened on Windows XP, only Vista? What should I do -
it looks like I cannot cleanup my computer anymore?
As a last resort - can I change the folder for tmp files that are needed for
SSIS packages execution, so I could exclude it somehow from the disk
cleanup?
Any advice would be greatly appreciated.
Thank you,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6899EAEE-6306-4D47-913B-BF503C445D66@.microsoft.com...
> Hi Peter
> "Peter Afonin" wrote:
>> Hello,
>> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
>> created several SSIS packages and run them under proxy account. At first
>> they worked just fine, but then all of them started to fail with the
>> error
>> messages like this one:
>> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
>> NonTransactableSql Execute SQL Task Description: An error occurred
>> with
>> the following error message: "Could not find file 'I:\Users\Peter
>> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
>> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
>> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
>> step failed.
>> If the cause is really in this tmp file, it doesn't make any sense. Yes,
>> I'm
>> deleting my tmp files periodically, so I don't have these files. It's
>> hard
>> to believe that SQL Server relies on tmp files that are often deleted.
>> Plus,
>> I was running the same packages on Windows XP for over a year and never
>> had
>> problems like this.
>> What else could it be and how to fix it? Is it a security issue?
>> I would appreciate your suggestions very much.
>> Thank you,
>> --
>> Peter Afonin
> I would suspect that the issue is probably with 'I:\Users\Peter
> Afonin\AppData\Local\Temp' not existing where is your temp directory set
> to?
> John|||Hi Peter
"Peter Afonin" wrote:
> John, I can confirm that SQL Server is indeed looking for these tmp files.
> 1. I've recreated my packages, they worked fine.
> 2. I removed all files from I:\Users\Peter Afonin\AppData\Local\Temp folder.
> The packages stopped working, giving me the error I mentioned before.
> 3. I put these tmp files back to this folder, the packages work fine again.
> This is something that I've never heard before and that doesn't make any
> sense. Why this never happened on Windows XP, only Vista? What should I do -
> it looks like I cannot cleanup my computer anymore?
> As a last resort - can I change the folder for tmp files that are needed for
> SSIS packages execution, so I could exclude it somehow from the disk
> cleanup?
> Any advice would be greatly appreciated.
> Thank you,
> Peter
>
SSIS may use files in a users temporary directory, if they have been
automatically generated or converted. You will need to check the datasources
and the package steps to see what they are. If necessary they can be moved to
a "common" directory that has the correct permissions for all users that will
run the package.
You may have found that removing the equivalent files in windows XP would
have had a similar result.
John|||Thank you, John, I'll edit my packages and see what's going on.
Peter
On Mar 22, 1:44 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> HiPeter
>
>
> "PeterAfonin" wrote:
> > John, I can confirm that SQL Server is indeed looking for these tmp files.
> > 1. I've recreated my packages, they worked fine.
> > 2. I removed all files from I:\Users\PeterAfonin\AppData\Local\Temp folder.
> > The packages stopped working, giving me the error I mentioned before.
> > 3. I put these tmp files back to this folder, the packages work fine again.
> > This is something that I've never heard before and that doesn't make any
> > sense. Why this never happened on Windows XP, only Vista? What should I do -
> > it looks like I cannot cleanup my computer anymore?
> > As a last resort - can I change the folder for tmp files that are needed for
> > SSIS packages execution, so I could exclude it somehow from the disk
> > cleanup?
> > Any advice would be greatly appreciated.
> > Thank you,
> >Peter
> SSIS may use files in a users temporary directory, if they have been
> automatically generated or converted. You will need to check the datasources
> and the package steps to see what they are. If necessary they can be moved to
> a "common" directory that has the correct permissions for all users that will
> run the package.
> You may have found that removing the equivalent files in windows XP would
> have had a similar result.
> John- Hide quoted text -
> - Show quoted text -

Tuesday, March 27, 2012

Error Executing Parallel SQL Tasks

I have three SQL tasks executing in parallel in an Integration Services package.

+-B-+
A-+-C-+-E
+-D-+

It starts with task A; then B, C, and D all execute in parallel; and finally task E runs after BCD are done.

B, C, and D are all Execute SQL tasks, all with the same connection manager. Here is their code:

B) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_B

C) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_C

D) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_D

Each one is setting a binary value to a package variable (using Result Set settings) based on the count of records from different tables.

This works with no problems when I run it against one server (development). But when I switch to the production server, task B and D both fail. I'v checked to make sure all of the temp tables exist in the database for that connection manager and that all three have the same connection manager - all is okay.

Here's the trickier part. When I'm still pointing to the production server and I run these tasks individually, they are all successful. It is only when they are attempting to run in parallel that they fail.

Here is the Output error:
Error: 0xC002F210 at Process Med?, Execute SQL Task: Executing the query "SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process FROM temp_B" failed with the following error: "Invalid object name 'temp_B'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

What could be causing this? I'm at a loss.

Why do they fail? Do you have an error message?

-Jamie

|||Sorry Jamie - I neglected to put in the error message at first. It's now in the original post.|||

perhaps the error message is a red herring. Can you use Profiler to check that everything is OK when the tasks get fired.

That's just an idea for diagnosis. I'm at a a loss as to what the problem might be!

-Jamie

|||

Problem solved.

Sorry about the errant post - it was actually not a parallel issue.

One of the previous steps changed the conenction manager's database setting and was doing it incorrectly. The tasks were hitting a false database. Not sure why task C didn't fail - but it's moot.

Thanks for your help.

Error executing Packaga from job

Hello, I finally could upload the package, and from the management studio interface I ran the package and it worked perfectly.

When I created a job, with one step only to execute that package, the job fails.

When I go to history it doesnt give me any details of what failed on the package or in the job

Date 24/01/2007 12:30:28
Log Job History (Carga datos ACH)

Step ID 1
Server ATLANTE\SQL2005
Job Name Carga datos ACH
Step Name Carga de datos de ach
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: ATLANTE\SYSTEM. The package execution failed. The step failed.

Maybe is the user that it tried to execute the package as?

How can I change it?

please delete this post. sorry for repeating|||I can't, but can someone merge some of Luis' threads that all revolve around the same issue?

Thanks,
Phil|||

this article describe solution to most comon issues when executing the package:

http://support.microsoft.com/kb/918760

|||

Hello, when I try to change the package protection level to server storage I got this

Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving to Xml.

|||Are you storing the packages as XML files or inside the DB? if you are using xmls files you can use DonSaveSensitive and the use package configurations to set the conection strings at run time as described in method 4 in that article.

Error execute SSIS package

What this?

An OLE DB error has occurred. Error code: 0x80040E14.

An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 2(error not found). Make sure you are accessing a local server via Windows security.".

Just a guess but...

Are you using SQL Server Destination by any chance?

If so, are you executing the package on the same server as your destination?

-Jamie

sql

Monday, March 26, 2012

Error during incremental processing of dimension

I have an integration services package that includes a data flow transformation that does an incremental processing for a dimension. The task executes successfully with a small amount of records in the data source query. However, when I attempt to process the large set, I get the following errors:

[Dimension Processing [1192]] Error: Parser: An error occurred during pipeline processing.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: An error occurred while the 'Last Name' attribute of the 'Consumer' dimension from the 'DataWarehouseOLAP' database was being processed.
[Dimension Processing [1192]] Error: File system error: The record ID is incorrect. Physical file: . Logical file: .
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: An error occurred while the 'Email Address' attribute of the 'Consumer' dimension from the 'DataWarehouseOLAP' database was being processed.
[Dimension Processing [1192]] Error: File system error: The record ID is incorrect. Physical file: . Logical file: .
[DTS.Pipeline] Error: The ProcessInput method on component "Dimension Processing" (1192) failed with error code 0x80004005. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
[DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0x80004005.
-

I am trying to figure out more information about these errors, but cannot figure out what the problem is. Can someone point me in the right direction?

Clayton

We just encountered the same error. Did you figure out what it was?|||No I did not. I am still stuck on it. I will let you know if I do.|||

Please log your situation in http://connect.microsoft.com/sql. If you willing to share your data to troubleshoot, make sure you provide your contact information.

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

|||

Hi,

I am facing the same issue. Can you please let me know if there is a solution for resloving this ?

Regards,

Dinesh Reddy N Y

|||

Sounds like you're exceeding the 4 GB limit for string stores. Do you have an attribute with a string key?

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

Wednesday, March 21, 2012

Error Deleteing Remote File

I am trying to delete a remote file as part of an SSIS package. The FTP Task I have to retrieve the file works fine. I use the same remote path variable and connection manager for both tasks. However, when the delete step executes I receive the error:

Error: 0xC002918E at FTP Task, FTP Task: Unable to delete remote files using "FTP Connection Manager 1".

Sounds like a permission issue.|||This is a known problem with the FTP task in SSIS trying to delete a file on a non-Windows FTP servers.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074276&SiteID=1

I do not know if SP2 fixes this problem or not.
|||I can delete the files from the FTP command line. I have a DTS package that uses a .bat file to do this, I just want to put it into SSIS. Thanks for the info.|||Is there a way to tell if the server is not Windows?|||HAs this issue been aknowledge by Microsoft? [Microsoft follow-up]|||

I don't understand your question. Your the closest thing to Microsoft that I have seen involved in any discussion in this area, anywhere I've looked.

Tim

|||Yes, it is still an active bug report, reported over 1 year ago.

See: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126207
|||No, you would have to know ahead of time what kind of server you are talking too.

However, there is a workaround on the thread I gave in the previous message. Basically, don't use the FTP task, use a script task and code it by hand.

|||We are aware of this bug and it will be fixed in the coming major release. Please contact CSS if you need a hotifx. Thanks

Error creating new SSIS project

When I start a new project the BI environment cannot open the DTSX package and I get only one tab with the message:

"microsoft visual studio is unable to load this document. Object reference not set to an instance of an object".

I tried uninstall and install of BI Development Studio as well as a repair install of Visual Studio 2005. None of which helped. Please help me to get this fixed.

Kind regards,

Neeva

Just to let you know, this problem seemed to have disappeared when I had to install SQL Server Express for a completely unrelated reason. I still don't understand it, but oh well..

Error creating new SSIS project

In my local client installation of the BI tools, I get the following error when simply creating an SSIS project and the default empty Package tries to display on the screen.

Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

I can use the Reporting Services designer with no problems, and I can use SSIS from the client tools on the server. It is just on my local PC that I get this error. I have completely uninstalled all the tools and reinstalled with no luck.

PLEASE HELP!

If anyone can help, please reply. I am unable to use SSIS AT ALL right now because a new package will only display this error message. And this is the purchased version, not the evaluation copy.

Here is the full message

Microsoft Visual Studio is unable to load this document:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

|||

I know it looks like I'm being a pest by bumping my post again, but I am not able to use SSIS at all on my PC. I HAVE TO get this resolved.

I am on Windows XP Pro fully patched and updated. I had SQL Express on my PC before and have since uninstalled it to see if that would help.

PLEASE HELP!!!

Sunday, February 26, 2012

Error concatenating string

I am trying to create a job that, as one of its steps, will kick off a
DTS package. As part of the command parameter, I need to concat a
system variable (@.@.SERVERNAME) to a constant string. I am receiving an
error about incorrect syntax near the +.

Here is the code for the job step.

-- Add the job steps
EXECUTE @.ReturnCode = msdb.dbo.sp_add_jobstep@.job_id = @.JobID,
@.step_id = 1,
@.step_name = N'Import OCC Series Data',
@.command = N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME,
@.database_name = N'',
@.server = N'',
@.database_user_name = N'',
@.subsystem = N'CmdExec',
@.cmdexec_success_code = 0,
@.flags = 2,
@.retry_attempts = 0,
@.retry_interval = 1,
@.output_file_name = N'',
@.on_success_step_id = 0,
@.on_success_action = 3,
@.on_fail_step_id = 0,
@.on_fail_action = 3
IF (@.@.ERROR <> 0 OR @.ReturnCode <> 0) GOTO QuitWithRollback

If I just try SELECT N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME, everything works fine. I even tried declaring a local
variable named @.command and setting it in the select statement, but no
dice."Jason" <JayCallas@.hotmail.com> wrote in message
news:f01a7c89.0402051028.4aa7015e@.posting.google.c om...
> I am trying to create a job that, as one of its steps, will kick off a
> DTS package. As part of the command parameter, I need to concat a
> system variable (@.@.SERVERNAME) to a constant string. I am receiving an
> error about incorrect syntax near the +.
> Here is the code for the job step.
> -- Add the job steps
> EXECUTE @.ReturnCode = msdb.dbo.sp_add_jobstep @.job_id = @.JobID,
> @.step_id = 1,
> @.step_name = N'Import OCC Series Data',
> @.command = N'DTSRun /F
> D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
> @.@.SERVERNAME,
> @.database_name = N'',
> @.server = N'',
> @.database_user_name = N'',
> @.subsystem = N'CmdExec',
> @.cmdexec_success_code = 0,
> @.flags = 2,
> @.retry_attempts = 0,
> @.retry_interval = 1,
> @.output_file_name = N'',
> @.on_success_step_id = 0,
> @.on_success_action = 3,
> @.on_fail_step_id = 0,
> @.on_fail_action = 3
> IF (@.@.ERROR <> 0 OR @.ReturnCode <> 0) GOTO QuitWithRollback
> If I just try SELECT N'DTSRun /F
> D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
> @.@.SERVERNAME, everything works fine. I even tried declaring a local
> variable named @.command and setting it in the select statement, but no
> dice.

You can't build a parameter value 'dynamically' like that, but assigning the
entire string to a variable first should work:

declare @.mycommand nvarchar(1000)
set @.mycommand = N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME

EXECUTE msdb.dbo.sp_add_jobstep
...
@.command = @.mycommand
...

What error did you get when you tried this?

Simon|||I ended up figuring that out and doing exactly what you suggested.
Something I did not know about passing parameters to stored
procedures...

The error I had gotten was
Incorrect syntax at '+'

Thanks for the help.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Error code: 0x80004005

I created a package that refreshes tables on one SQL Server to another SQL Server. First, I use an ExecuteSQL task to truncate the tables. Then I use a Data Flow task to copy the tables from one server to the other. Finally I update a log table. It was working fine with four tables. I added another table to the refresh and now I get these error messages:

[Source - RbcAcctSegment [1096]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

I made a few changes in the Data Flow task. In the Properties of the Destination components I changed the OpenRowset property to include the database name beside the table name. Not all the Destination components had the database name.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

|||Now that you mention, I do remember we did have a similar error when we had around 20 in a data flow and then we moved some of them out to a new data flow and it worked fine. I had to put a precedence between the two.

Error code: 0x80004005

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

error code from DTEXEC not 0 nor 1

I would like to send back to MS-DOS (ERRORLEVEL) an error code 2 ( different from 0 and 1) via a scripting Task.

Our package are started with the DTEXEC Utility.

In general, how can i send back a flag saying "There were warnings" during the execution of a Package

Warnings can happen with successful package executions, and for that matter, so can errors.

There are a numerous ways to figure out there were warnings though, such that a shell caller is aware of that fact.

One, capture the console output from dtexec and look through the captured text for the warning event.

Two, create a console utility which calls Package.Execute() and iterates through the .Warnings collection. If the count > 0, return what you want as the process exit code.

Three, use logging. Configure the package to use the native SSIS logging facilities to write log entires. Read the produced log provider for warning events.

Four, use a package level OnWarning event handler. Inside the event handler, set something external to the package (file, db, message queue, doesn't matter) which is readable post-execution.

Thursday, March 29, 2012

Error executing xp_cmdshell from within a SQL task in a DTS package...

Error executing SSIS package

Error executing SSIS package

Error executing SSIS package

Tuesday, March 27, 2012

Error Executing Parallel SQL Tasks

Error executing Packaga from job

Error execute SSIS package

Monday, March 26, 2012

Error during incremental processing of dimension

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

Wednesday, March 21, 2012

Error Deleteing Remote File

Error creating new SSIS project

Error creating new SSIS project

Sunday, February 26, 2012

Error concatenating string

Error code: 0x80004005

Error code: 0x80004005

error code from DTEXEC not 0 nor 1

Error accessing report

Blog Archive

About Me