Showing posts with label legacy. Show all posts
Showing posts with label legacy. Show all posts

Tuesday, March 27, 2012

Error when schedule a job in SQL 2005

Hi,

I have a SSIS package that contains an Execute DTS 2000 process. This DTS 2000 is calling a legacy package, which resides on the same server. The legacy package is just to import a flat file into the database. When i right click and execute this package, it runs perfectly without any errors. However, if i try to schedule this package as a job, it keeps failing.

I checked the flat file source for the permission, it does have the account of the executor of the package. In the view history, i didn't see any more information about why it is failing. It keeps saying "The job failed. The Job was invoked by Schedule 10...."

Does anyone have any ideas?

Did you try to turn on logging so you could get better error details?|||

Thanks, I turned on the log and it wrote to the application log events saying. Is there another log event in SQL 2005? I only saw it said "View History" in the scheduled job.

Status: Failed - Invoked on: 2006-11-06 13:56:00 - Message: The job failed. The Job was invoked by Schedule 24 (Test Schedule). The last step to run was step 1 (RUN ImportData)

|||See this KB about turning on logging and general troubleshooting of SSIS packages under Agent:
http://support.microsoft.com/kb/918760

Monday, March 26, 2012

Error when opening a Lookup in a Legacy DTS package

Hi all,

the SQL Management Studio keeps crashing out on me everytime i try to open a Lookup in one of my DTS packages i am using in the Legacy section.

I am copying the DTS package across and need to change the server connections (which i do), but then i was getting a permissions based error when the package ran when it tries to access the Lookup.

I tried to open the Lookup and the SQL Management Studio hanged when it tried to display the details for the lookup. It's done this many times and i have tried different files incase one was corrupted to no avail.

Anyone have any ideas of what i can try?

Thanks

Jordan

Hi Jordan,

Want to know the following:

1) Have you installed DTS 2000 Designer utility from the Feature Pack release?

2) Once the above utility is installed and then importing the DTS package into Legacy section of Management Studio, are you able to successfully decrypt the Package with password you have used to encrypt and open it successfully?

3) Assuming that this file is corrupt, another way is to embed your DTS Package in a newly created SSIS Package using DTS 2000 Task.

Hope ensuring the above steps should solve your problem.

Thanks

Subhash Subramanyam

|||

Hi Subhash,

1) How do i determine this? I can already view the DTS package in the Legacy section of 2005, does this mean it is already installed?

2) To install the package i have Saved it out of SQL 2000 as a DTS file and opened the package in SQL 2005 and saved it to the server. Should i be doing something else?

3) i haven't looked at SSIS yet. I'm not sure what that would involve.

Thanks

Jordan

Subhash512525 wrote:

Hi Jordan,

Want to know the following:

1) Have you installed DTS 2000 Designer utility from the Feature Pack release?

2) Once the above utility is installed and then importing the DTS package into Legacy section of Management Studio, are you able to successfully decrypt the Package with password you have used to encrypt and open it successfully?

3) Assuming that this file is corrupt, another way is to embed your DTS Package in a newly created SSIS Package using DTS 2000 Task.

Hope ensuring the above steps should solve your problem.

Thanks

Subhash Subramanyam

Monday, March 19, 2012

Error when connecting to SQL Express

Hi - can anyone please help?

I am using SQL Express 2005 - and have an asp (yes legacy asp) site running locally. It works ok, until I try and connect to the server from another PC.

The error message I get is:

******

Microsoft OLE DB Provider for SQL Servererror '80004005'

Cannot open database "fixit" requested by the login. The login failed.

/fixitnew/fixit_login.asp, line 30

******

Line 30, is where I open the connection to the database.

My connection string is:

myConn = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=fixit;Data Source=misinvaknb01\sqlexpress;"

Can anyone please help?

Thanks in advance,

Mark

Hi

Default user has no permission to access fixit database . Follow those steps:

In Management Studio choose Security->Logins ->WindowsUserName->right click choose property->UserMapping -->Checkfixit database

Hope it helps.