Showing posts with label continue. Show all posts
Showing posts with label continue. Show all posts

Monday, March 26, 2012

Error during install of SqlServer 2005 64 Bit edition - please help!

Hi Folks,

I'm receiving an error when i'm trying to setup a maintenance plan. I'm getting weird errors (and cannot continue) and i'm thinking it's related to a 32 bit error i received during installation on a 64 bit edition.

Background
We have a sql server behind hosted on a dedicated 64 bit box out of SanFran. The hosting company installed the 32 bit version of SqlServer 2005 standard on the box and I requested them to remove it and put the 64 bit edition on. They removed the 32 bit edition and installed the 64 bit edition. So far so good. I installed sp1 and that was fine. I then tried to start a MAINTENCE PLAN and was denied -> the component was not installed. I've asked them to install the component and they did, but they recorded an error during the install. The error screen shot is here: http://img525.imageshack.us/img525/5089/errormessagehs4.png

Now i cannot drop any tasks onto the maintenence plan ... so i'm assuming it's related to the above error. Is there any way i can determine what the 32 bit component is, remove it and re-install the correct component? Is there an error log somewhere where i can check things?

This is stopping me from setting up any backup plans :(

Regards,
Justin.

I've tried to google for more info and still have come up blank - anyone know of any clues to help, please?|||

This is an issue where Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog when you toggle between 32-bit and 64-bit installs. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

Then your install should work fine.

Thanks,
Sam Lester (MSFT)

|||

Thanks HEAPS Sam for the post.


>>Sam said:: Then your install should work fine.

So i should then re-install the component that is required for maintenance plans?

Thanks soooo much for reading my post and replying!!

|||

I don't claim to know much about IS & maintenance plans, but that error is due to being able to only register one entry in COM+ at a time. My guess would be that reinstalling after fixing this error should make IS function as normal again. :)

Thanks,
Sam

|||

Thanks again sam - i know this post is a bit late, but i finally got around to removing the 32bit com+ and then installed Sp2 (which was why i waited for so long).

Things look fine - cheers mate.

Error during install of SqlServer 2005 64 Bit edition - please help!

Hi Folks,

I'm receiving an error when i'm trying to setup a maintenance plan. I'm getting weird errors (and cannot continue) and i'm thinking it's related to a 32 bit error i received during installation on a 64 bit edition.

Background
We have a sql server behind hosted on a dedicated 64 bit box out of SanFran. The hosting company installed the 32 bit version of SqlServer 2005 standard on the box and I requested them to remove it and put the 64 bit edition on. They removed the 32 bit edition and installed the 64 bit edition. So far so good. I installed sp1 and that was fine. I then tried to start a MAINTENCE PLAN and was denied -> the component was not installed. I've asked them to install the component and they did, but they recorded an error during the install. The error screen shot is here: http://img525.imageshack.us/img525/5089/errormessagehs4.png

Now i cannot drop any tasks onto the maintenence plan ... so i'm assuming it's related to the above error. Is there any way i can determine what the 32 bit component is, remove it and re-install the correct component? Is there an error log somewhere where i can check things?

This is stopping me from setting up any backup plans :(

Regards,
Justin.

I've tried to google for more info and still have come up blank - anyone know of any clues to help, please?|||

This is an issue where Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog when you toggle between 32-bit and 64-bit installs. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

Then your install should work fine.

Thanks,
Sam Lester (MSFT)

|||

Thanks HEAPS Sam for the post.


>>Sam said:: Then your install should work fine.

So i should then re-install the component that is required for maintenance plans?

Thanks soooo much for reading my post and replying!!

|||

I don't claim to know much about IS & maintenance plans, but that error is due to being able to only register one entry in COM+ at a time. My guess would be that reinstalling after fixing this error should make IS function as normal again. :)

Thanks,
Sam

|||

Thanks again sam - i know this post is a bit late, but i finally got around to removing the 32bit com+ and then installed Sp2 (which was why i waited for so long).

Things look fine - cheers mate.

Friday, February 24, 2012

Error catching in SSIS

I have a package that is failing parsing a CSV file. I want to write the failing line to an error file and continue processing. I've added error output to the flat file source, that didn't work. I've added an onerror event handler to the data flow task, that didn't work. I've added an event handler to the package, that didn't work. How can i output the offending line but not have the process fail?

Go to the Error Output page on the Flat File Source editor and set appropriate Error and Truncation values to Redirect. After this connect your error output to a Flat file destination where you can take care of erroneous rows.

Thanks,

Bob

|||Thanks, but that isn't it. I've got it set to redirect. The error is

Error: 0xC0202055 at Data Flow Task, Flat File Source [1]: The column delimiter for column "Column 3" was not found.

It is being caused by an embeded double quote in the source CSV file. It's escaped to "" and the parser blows up. It dosent go to the error output. and i can't seem to catch the error, it kills the process.

|||

The flat file parser cannot handle embedded quotes. You will have to load qualified data and post-process it using script or derived columns.

Thanks,

Bob

Error catching in SSIS

I have a package that is failing parsing a CSV file. I want to write the failing line to an error file and continue processing. I've added error output to the flat file source, that didn't work. I've added an onerror event handler to the data flow task, that didn't work. I've added an event handler to the package, that didn't work. How can i output the offending line but not have the process fail?

Go to the Error Output page on the Flat File Source editor and set appropriate Error and Truncation values to Redirect. After this connect your error output to a Flat file destination where you can take care of erroneous rows.

Thanks,

Bob

|||Thanks, but that isn't it. I've got it set to redirect. The error is

Error: 0xC0202055 at Data Flow Task, Flat File Source [1]: The column delimiter for column "Column 3" was not found.

It is being caused by an embeded double quote in the source CSV file. It's escaped to "" and the parser blows up. It dosent go to the error output. and i can't seem to catch the error, it kills the process.

|||

The flat file parser cannot handle embedded quotes. You will have to load qualified data and post-process it using script or derived columns.

Thanks,

Bob