Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Executing Package on 64 bit machine Expand / Collapse
Author
Message
Posted Friday, September 4, 2009 10:47 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, December 15, 2010 5:49 AM
Points: 32, Visits: 82
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.

Post #783078
Posted Friday, September 4, 2009 11:05 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:27 PM
Points: 1,117, Visits: 2,219
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?


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #783092
Posted Friday, September 4, 2009 11:16 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, December 15, 2010 5:49 AM
Points: 32, Visits: 82

I have put the code under try catch but then also I am not getting any error...

Its really frustrating

Post #783100
Posted Friday, September 4, 2009 11:25 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:27 PM
Points: 1,117, Visits: 2,219
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.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #783108
Posted Friday, September 4, 2009 11:51 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, December 15, 2010 5:49 AM
Points: 32, Visits: 82

I have kept the SSIS logging on but since the package is not getting executed logging is also not done...
Post #783117
Posted Friday, September 4, 2009 12:02 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:27 PM
Points: 1,117, Visits: 2,219
amit (9/4/2009)

I have kept the SSIS logging on but since the package is not getting executed logging is also not done...


Dump the error to a text file. This should be easy to setup.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #783123
Posted Saturday, September 5, 2009 4:28 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, December 15, 2010 5:49 AM
Points: 32, Visits: 82
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
Post #783302
Posted Saturday, September 5, 2009 7:23 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:27 PM
Points: 1,117, Visits: 2,219
These doesn't look like errors. Please check again.

---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #783331
Posted Monday, September 7, 2009 2:49 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, December 15, 2010 5:49 AM
Points: 32, Visits: 82
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
Post #783665
Posted Monday, September 7, 2009 4:03 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:27 PM
Points: 1,117, Visits: 2,219
It looks like you have issue with the login. What package protection level have you used?

---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #783685
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse