Showing posts with label imported. Show all posts
Showing posts with label imported. Show all posts

Monday, March 12, 2012

Error when clicking OK on edit of task

I've got a package that was imported from SQL 2000 into SQL 2005. I'm trying to edit it in Business Int. Dev Studio. When I open what used to be a data pump step in 2000, I'm able to edit items. However, when I click OK, it puts an error right below the buttons:

"" is not a value type

And it won't let me save my changes. I have no idea where this error is coming from. All the data pumps in this package cause the same error. Your help is appreciated.Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.|||

arc_dev wrote:

Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.

Well done for picking this up. Did you use the migration wizard? If so, this is a bug in the migration wizard. Could you report it at Microsoft Connect?

-Jamie

|||I just created a bug report with screen captures of what it does.

Wednesday, February 15, 2012

Error running schedule job

I have this SSIS Package that it works when I run it on development on Visual Studio. But when I imported it and schedule the job, it gives me the following error:

Executed as user: MAINOFFICE\ASPNET. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:38:39 PM Error: 2007-11-05 14:38:41.02 Code: 0xC0202009 Source: Export_WHSCANP Connection manager "10.5.1.10.DRDB400.aspnet1" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 Session" Hresult: 0x80004005 Description: "CWBSY0002 - Password for user ASPNET on server 10.5.1.10 is not correct ". End Error Error: 2007-11-05 14:38:41.04 Code: 0xC020801C Source: Data Flow Task OLE DB Destination [801] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "10.5.1.10.DRDB400.aspnet1" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnec... The package execution fa... The step failed.

This is trying to get a table from the SQL server and copy it to an IBM AS400 server. Any ideas?

Thanks,

Erick

Is the connection information the same in the new environment as it was in development?

|||

It is, I didnt change anything I just uploaded the working SSIS Package to the integration services and call it from a job schedule. The job runs in the integration services, but the schedules fails.

|||

I found a very helpfull article on this problemhttp://www.cubido.at/Blog/tabid/176/EntryID/71/Default.aspx