September 4, 2009 at 10:47 am
Hi All,
I have developed an asp.net 2008, ssis application on 32 bit machine, which is executing the package successfully and even doing the logging into the system table.
For executing the package through asp.net I have used Package.Execute()
But when I have deployed the application on 64 bit windows 2003, I am unable to execute the application and that to with no errors...
I am not getting what setting needs to be changed for 64 bit machine.
September 4, 2009 at 11:05 am
amit (9/4/2009)
Hi All,I have developed an asp.net 2008, ssis application on 32 bit machine, which is executing the package successfully and even doing the logging into the system table.
For executing the package through asp.net I have used Package.Execute()
But when I have deployed the application on 64 bit windows 2003, I am unable to execute the application and that to with no errors...
I am not getting what setting needs to be changed for 64 bit machine.
Can you tell us what is the error you are getting?
September 4, 2009 at 11:16 am
I have put the code under try catch but then also I am not getting any error...
Its really frustrating
September 4, 2009 at 11:25 am
amit (9/4/2009)
I have put the code under try catch but then also I am not getting any error...Its really frustrating
Amit,
Log the error in your catch handler . Try to use the SSIS logging facilities . Another solution, which doesn't depend on SSIS is to simply log the error to a file and then examine the file.
September 4, 2009 at 11:51 am
I have kept the SSIS logging on but since the package is not getting executed logging is also not done...
September 4, 2009 at 12:02 pm
September 5, 2009 at 4:28 am
These are the following errors I am getting...
2009-09-05 09:55:52 W3SVC1 10.0.0.11 POST /Default.aspx - 80 - 10.0.0.11 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+WOW64;+SV1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 401 1 0
2009-09-05 09:55:52 W3SVC1 10.0.0.11 POST /Default.aspx - 80 Administrator 10.0.0.11 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+WOW64;+SV1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0
September 5, 2009 at 7:23 am
September 7, 2009 at 2:49 am
These are the following Errors :
Error is SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D
Description: "Login failed for user 'sa'.". -1071636471 Package 0
Error is SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "10.0.0.11.Database.sa" failed with error
code 0xC0202009. There may be error messages posted before this with more information on why the
AcquireConnection method call failed. COM error object information is available. Source: "Package"
error code: 0xC0202009 Description: "SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult:
0x80040E4D Description: "Login failed for user 'sa'.". ". -1071611876 Package 0
Error is SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D
Description: "Login failed for user 'sa'.". -1071636471 Package 0
Error is SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "10.0.0.11.Database.sa" failed with error
code 0xC0202009. There may be error messages posted before this with more information on why the
AcquireConnection method call failed. -1071611876 Data Flow Task 0
Error is component "OLE DB Destination" (14) failed validation and returned error code 0xC020801C.
-1073450985 Data Flow Task 0
Error is One or more component failed validation. -1073450996 Data Flow Task 0
Error is There were errors during task validation. -1073594105 Data Flow Task -1073594105
September 7, 2009 at 4:03 am
September 7, 2009 at 6:04 am
This particular code executes properly when executed on 32 bit windows 2003 with no errors
Its throwing error on 64 bit machine only.
package functionality is importing excel data into sql database... so just the sql credentials have been entered.
September 7, 2009 at 8:54 am
amit (9/7/2009)
This particular code executes properly when executed on 32 bit windows 2003 with no errorsIts throwing error on 64 bit machine only.
package functionality is importing excel data into sql database... so just the sql credentials have been entered.
Again my question what is the package protection level in use?
September 7, 2009 at 9:16 am
DontSaveSensitive
September 7, 2009 at 10:08 am
amit (9/7/2009)
DontSaveSensitive
You said you are using SQL Server credentials to login. But with this setting unless you provide the password with external configuration file, the connection will not work.
You said you already had this package working from another machine. Do you use exactly same user account on both machines?
September 7, 2009 at 10:50 am
The package on both the machines are different but have the same functionality with diffrent sql connection.
the common is the asp.net code on both the machines
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply