Error installing SQL Server Management Studio Express on Windows Vista RC1

Hello NG,

After installing SQL Server 2005 Express Edition on Windows Vista RC1, I wanted to install also the Managent Studio but I always receive the following error message:

"Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 29506."

Where can I find more infos about this error-code?

Anybody knows this problem?

Thank in advance for every help.

You might want to try installing under rasied permissions for the user... Also from memory the install of the express products on vista had not been approved (Supported) and MS were working on it with the Newer SP for the express products. You might want to check it out with one of the guys from MS. Also if you could translate the error message to english it might help some of use read what is going on....

|||I′ve got the same error. I started a cmd-shell as an Administrator and started the MSI package from there. This works.

HTH
Alexej Kucher

|||

Hi...

How can I start a cmd_shell as an Administrator.

thanks

|||Just right-click the command shell icon and choose "run as..." .Enter the admin credentials.

Error installing SQL Server Management Studio Express on Windows Vista RC1

Hello NG,

After installing SQL Server 2005 Express Edition on Windows Vista RC1, I wanted to install also the Managent Studio but I always receive the following error message:

"Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 29506."

Where can I find more infos about this error-code?

Anybody knows this problem?

Thank in advance for every help.

You might want to try installing under rasied permissions for the user... Also from memory the install of the express products on vista had not been approved (Supported) and MS were working on it with the Newer SP for the express products. You might want to check it out with one of the guys from MS. Also if you could translate the error message to english it might help some of use read what is going on....

|||I′ve got the same error. I started a cmd-shell as an Administrator and started the MSI package from there. This works.

HTH
Alexej Kucher

|||

Hi...

How can I start a cmd_shell as an Administrator.

thanks

|||Just right-click the command shell icon and choose "run as..." .Enter the admin credentials.

Error installing SQL Server Management Studio Express on Windows Vista RC1

Hello NG,

After installing SQL Server 2005 Express Edition on Windows Vista RC1, I wanted to install also the Managent Studio but I always receive the following error message:

"Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 29506."

Where can I find more infos about this error-code?

Anybody knows this problem?

Thank in advance for every help.

You might want to try installing under rasied permissions for the user... Also from memory the install of the express products on vista had not been approved (Supported) and MS were working on it with the Newer SP for the express products. You might want to check it out with one of the guys from MS. Also if you could translate the error message to english it might help some of use read what is going on....

|||I′ve got the same error. I started a cmd-shell as an Administrator and started the MSI package from there. This works.

HTH
Alexej Kucher|||

Hi...

How can I start a cmd_shell as an Administrator.

thanks

|||Just right-click the command shell icon and choose "run as..." .Enter the admin credentials.

Error installing SQL Server 2005 on Vista

Here's the ERRORLOG:

2007-05-15 01:52:05.69 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 6.0 (Build 6000: )

2007-05-15 01:52:05.69 Server (c) 2005 Microsoft Corporation.
2007-05-15 01:52:05.69 Server All rights reserved.
2007-05-15 01:52:05.69 Server Server process ID is 3860.
2007-05-15 01:52:05.69 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-05-15 01:52:05.69 Server This instance of SQL Server last reported using a process ID of 3252 at 5/15/2007 1:51:57 AM (local) 5/15/2007 6:51:57 AM (UTC). This is an informational message only; no user action is required.
2007-05-15 01:52:05.69 Server Registry startup parameters:
2007-05-15 01:52:05.69 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-05-15 01:52:05.69 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-05-15 01:52:05.69 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-05-15 01:52:05.69 Server Command Line Startup Parameters:
2007-05-15 01:52:05.69 Server -m SqlSetup
2007-05-15 01:52:05.69 Server SqlSetup
2007-05-15 01:52:05.69 Server -Q
2007-05-15 01:52:05.69 Server -q SQL_Latin1_General_CP1_CI_AS
2007-05-15 01:52:05.69 Server -T 4022
2007-05-15 01:52:05.69 Server -T 3659
2007-05-15 01:52:05.69 Server -T 3610
2007-05-15 01:52:05.69 Server -T 4010
2007-05-15 01:52:05.70 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-05-15 01:52:05.70 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-05-15 01:52:05.78 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-05-15 01:52:05.78 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-05-15 01:52:07.85 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-05-15 01:52:07.85 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-05-15 01:52:07.85 spid5s Warning ******************
2007-05-15 01:52:07.85 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2007-05-15 01:52:07.85 spid5s Starting up database 'master'.
2007-05-15 01:52:08.17 spid5s SQL Trace ID 1 was started by login "sa".
2007-05-15 01:52:08.22 spid5s Starting up database 'mssqlsystemresource'.
2007-05-15 01:52:08.61 spid8s Starting up database 'model'.
2007-05-15 01:52:08.61 Server Error: 17182, Severity: 16, State: 1.
2007-05-15 01:52:08.61 Server TDSSNIClient initialization failed with error 0x2, status code 0x80.
2007-05-15 01:52:08.61 Server Error: 17182, Severity: 16, State: 1.
2007-05-15 01:52:08.61 Server TDSSNIClient initialization failed with error 0x2, status code 0x1.
2007-05-15 01:52:08.61 Server Error: 17826, Severity: 18, State: 3.
2007-05-15 01:52:08.61 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-05-15 01:52:08.61 Server Error: 17120, Severity: 16, State: 1.
2007-05-15 01:52:08.61 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

It is a good idea to read this blog about Vista/SQL Server issues.

SQL Server 2005 Express and Vista
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

I've already read that, didn't help. That blog is basically talking about giving users sysadmin rights.

The problem I'm having is related to the TNSSNIClient, and I'm guessing it's related to SSL certificates, but that's as far as I can go with it. I've googled every error message, every event code, and every combination of words that relate to the problem, and haven't found a solution yet.

|||I've tried everything I can think of... Anyone?sql

Error installing SQL Server 2005 editions on Windows VISTA

There are numerous posts regarding this error when installing SQL Server 2005 on Windows Vista RTM thus I am starting a new thread in order to get resolution one way or another:

SQL Server Setup failed to execute a command for server configuration. The error was [SQL Native Client]Windows user or group "\USERNAME\SQLServer2005MSFTEUser$USERNAME$MSSQLSERVER" not found. Check the name again...

The error occurs when installing SQL Server 2005 Developer Edition, SQL Server Express SP1, SQL Server Express SP2 CTR (with or without the SP2 Toolkit package installed beforehand). The error occurs with or without UAC.

The installation then fails. Please advise if you have any insights. SQL Server Express SP2 CTR was announced as a workable version for Vista... note that this is not the case.

I am just stating that I have the same problem.

|||

This is a problem on Vista if case sensitive collation is chosen and Windows computer name includes lower case characters.

Possible workarounds:

1. Change the computer name with upper case.

Since Vista does not allow to change a computer name to the same name with only case difference, this workaround requires two steps, changing to the different name first (ComputerName to ComputerNameX for example) and then changing to the original name with upper case (ComputerNameX -> COMPUTERNAME).

2. Change the collation that the customer's product uses from case sensitive (including binary) to case insensitive.

|||

Well thanks. That has worked

Microsoft really must make this a little more public so other people don't jump in this hole

|||

Some one at Microsoft connect has just confirmed that this is a known error.

quote "Also there is a known issue with install SP2 on Vista machines where the Machine name has lower case letters or other 'special' characters and you are using the non-default collation "

In fact, as we know, its a propblem with the install whatever service pack.

|||Milos,

Thank you. That worked correctly.

Considering the time that has been and is likely to continue to be frustratingly wasted by a great number of people, I agree that this mixed computer name case issue should be better documented. If only I could get the past 2 days of my life back.

Thanks again.|||SQL Server 2005 SP2 isn't released yet, and Microsoft has stated (repeatedly) that non-SP2 installs are not supported on Vista.|||

No, in fact Microsoft state that SQL Server 2005 is not supported on Vista without SP2.

I had downloaded the beta release of the service pack ready to apply but in order to apply the service pack, guess what? - you have to install the base version of the software!

So next time think before you make unhelpful and supercilious remarks.

|||

Understood - I think we're saying the same thing.

Also, it should be noted that you can *install* the software, it just isn't *supported* without SP2. That's because there are some changes in SP2 that make it work properly within the environment. Yes, you will still have to install the base package.

You'll notice in the readme file that comes with SP2 that it will have specific instructions for Vista installs, which is why I made these comments - which I think are both helpful and non-supercillious. No harm intended, I think you misunderstood my post.

|||Thank you for your comments. I could never get SQL Server 2005 installed on VISTA in order to apply the SP2. The setup would crash near the very end of the base installation as the SQL Server Native configuration string update could not discriminate between mixed case computer names when binary sort order was selected.

This was a very difficult problem to work through as the primary documentation discussing SQL Server and Vista stated that SQL Server SP2 was required. However, to apply SQL Server SP2 you had to get SQL Server installed. Thus, the catch 22 for those who were trying to install SQL Server 2005 using the new binary sort order option.

Right now, it seems that many of the bug fixes are found only by posting to newsgroups or forums such as this. People at Microsoft knew of this particular binary mixed computer name configuration string error and were likely fixing this in SP2, etc. However, the public didn't and thus we spent days of wasted frustrated time simply to get an error at the very end of the SQL Server setup procedure. Wouldn't it make sense for Microsoft to add on to the MSDN knowledge base "bug snippets" such as found in this forum itself. So instead of having days of human life wasted in installation frustration, one could do a search in MSDN online for the error message that I posted above, and the solution (as found above by the kind person) would be presented?|||

I hear you. I've spent lots of time on things only to find out later that someone had the info to help me all along! I think in Microsoft's defense that they haven't released patches for this issue yet, so they are working on not having to document them. If it turns out that you have to "work your way around" something, we want to make sure that we document it correctly, in the 9 languages we support, and subject to the legal and other rules we face in hundreds of countries around the world, and then test on the thousands of systems (SAP, custom apps, clustering, PDA's, replication, etc.) that we run on. That takes time, which is why we're asking for patience as we work through the issues.

The danger of posting something before we are done working on it is that it might "live" after the correct procedure is developed when the product is actually supported on Vista. Then we run into the problem of people possibly damaging their systems using a workaround for a problem we've corrected another way. So in effect, we're kind of in a catch-22 as well!

Luckily, Microsoft hosts these forums for exactly this reason. It give all of us DBAs a chance to hash this out in an informal setting, and helps the company feel the pain points of its customers. This lets us fix the problems before we support the product. These posts are VERY valuable, and we thank you all for making them. We're here to help.

|||

The funny part of this is that the day you posted this complaint is the same day Microsoft published the KB article on the topic.

http://support.microsoft.com/kb/929105 (Yes, it is about express but the concept is the same)

Chill out.. Microsoft is not some conglomerate conspiracy trying to screw the people that use thier software. That would be counter intuitive.

Since people are so trigger happy to sue the *** out of Microsoft whenever they misspell a word or misstate a concept it takes them time to edit/approve/audit the items that are published. Its the price of being a large company.

-David Sandor

|||This worked after changing the computer name to all caps (very offensive) and removing non-standard characters (like Underscore) when installed a case senitive collations are used. Of course I like to use things like Spaces in my tables and procedures! I would like to be able to use spaces in computer names as well, but then I just name the computer after what it is. I was finally able to get the software to install.|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - loke me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - like me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

Error installing SQL Server 2005 editions on Windows VISTA

There are numerous posts regarding this error when installing SQL Server 2005 on Windows Vista RTM thus I am starting a new thread in order to get resolution one way or another:

SQL Server Setup failed to execute a command for server configuration. The error was [SQL Native Client]Windows user or group "\USERNAME\SQLServer2005MSFTEUser$USERNAME$MSSQLSERVER" not found. Check the name again...

The error occurs when installing SQL Server 2005 Developer Edition, SQL Server Express SP1, SQL Server Express SP2 CTR (with or without the SP2 Toolkit package installed beforehand). The error occurs with or without UAC.

The installation then fails. Please advise if you have any insights. SQL Server Express SP2 CTR was announced as a workable version for Vista... note that this is not the case.

I am just stating that I have the same problem.

|||

This is a problem on Vista if case sensitive collation is chosen and Windows computer name includes lower case characters.

Possible workarounds:

1. Change the computer name with upper case.

Since Vista does not allow to change a computer name to the same name with only case difference, this workaround requires two steps, changing to the different name first (ComputerName to ComputerNameX for example) and then changing to the original name with upper case (ComputerNameX -> COMPUTERNAME).

2. Change the collation that the customer's product uses from case sensitive (including binary) to case insensitive.

|||

Well thanks. That has worked

Microsoft really must make this a little more public so other people don't jump in this hole

|||

Some one at Microsoft connect has just confirmed that this is a known error.

quote "Also there is a known issue with install SP2 on Vista machines where the Machine name has lower case letters or other 'special' characters and you are using the non-default collation "

In fact, as we know, its a propblem with the install whatever service pack.

|||Milos,

Thank you. That worked correctly.

Considering the time that has been and is likely to continue to be frustratingly wasted by a great number of people, I agree that this mixed computer name case issue should be better documented. If only I could get the past 2 days of my life back.

Thanks again.|||SQL Server 2005 SP2 isn't released yet, and Microsoft has stated (repeatedly) that non-SP2 installs are not supported on Vista.|||

No, in fact Microsoft state that SQL Server 2005 is not supported on Vista without SP2.

I had downloaded the beta release of the service pack ready to apply but in order to apply the service pack, guess what? - you have to install the base version of the software!

So next time think before you make unhelpful and supercilious remarks.

|||

Understood - I think we're saying the same thing.

Also, it should be noted that you can *install* the software, it just isn't *supported* without SP2. That's because there are some changes in SP2 that make it work properly within the environment. Yes, you will still have to install the base package.

You'll notice in the readme file that comes with SP2 that it will have specific instructions for Vista installs, which is why I made these comments - which I think are both helpful and non-supercillious. No harm intended, I think you misunderstood my post.

|||Thank you for your comments. I could never get SQL Server 2005 installed on VISTA in order to apply the SP2. The setup would crash near the very end of the base installation as the SQL Server Native configuration string update could not discriminate between mixed case computer names when binary sort order was selected.

This was a very difficult problem to work through as the primary documentation discussing SQL Server and Vista stated that SQL Server SP2 was required. However, to apply SQL Server SP2 you had to get SQL Server installed. Thus, the catch 22 for those who were trying to install SQL Server 2005 using the new binary sort order option.

Right now, it seems that many of the bug fixes are found only by posting to newsgroups or forums such as this. People at Microsoft knew of this particular binary mixed computer name configuration string error and were likely fixing this in SP2, etc. However, the public didn't and thus we spent days of wasted frustrated time simply to get an error at the very end of the SQL Server setup procedure. Wouldn't it make sense for Microsoft to add on to the MSDN knowledge base "bug snippets" such as found in this forum itself. So instead of having days of human life wasted in installation frustration, one could do a search in MSDN online for the error message that I posted above, and the solution (as found above by the kind person) would be presented?|||

I hear you. I've spent lots of time on things only to find out later that someone had the info to help me all along! I think in Microsoft's defense that they haven't released patches for this issue yet, so they are working on not having to document them. If it turns out that you have to "work your way around" something, we want to make sure that we document it correctly, in the 9 languages we support, and subject to the legal and other rules we face in hundreds of countries around the world, and then test on the thousands of systems (SAP, custom apps, clustering, PDA's, replication, etc.) that we run on. That takes time, which is why we're asking for patience as we work through the issues.

The danger of posting something before we are done working on it is that it might "live" after the correct procedure is developed when the product is actually supported on Vista. Then we run into the problem of people possibly damaging their systems using a workaround for a problem we've corrected another way. So in effect, we're kind of in a catch-22 as well!

Luckily, Microsoft hosts these forums for exactly this reason. It give all of us DBAs a chance to hash this out in an informal setting, and helps the company feel the pain points of its customers. This lets us fix the problems before we support the product. These posts are VERY valuable, and we thank you all for making them. We're here to help.

|||

The funny part of this is that the day you posted this complaint is the same day Microsoft published the KB article on the topic.

http://support.microsoft.com/kb/929105 (Yes, it is about express but the concept is the same)

Chill out.. Microsoft is not some conglomerate conspiracy trying to screw the people that use thier software. That would be counter intuitive.

Since people are so trigger happy to sue the *** out of Microsoft whenever they misspell a word or misstate a concept it takes them time to edit/approve/audit the items that are published. Its the price of being a large company.

-David Sandor

|||This worked after changing the computer name to all caps (very offensive) and removing non-standard characters (like Underscore) when installed a case senitive collations are used. Of course I like to use things like Spaces in my tables and procedures! I would like to be able to use spaces in computer names as well, but then I just name the computer after what it is. I was finally able to get the software to install.|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - loke me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - like me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

Error installing SQL Server 2005 editions on Windows VISTA

There are numerous posts regarding this error when installing SQL Server 2005 on Windows Vista RTM thus I am starting a new thread in order to get resolution one way or another:

SQL Server Setup failed to execute a command for server configuration. The error was [SQL Native Client]Windows user or group "\USERNAME\SQLServer2005MSFTEUser$USERNAME$MSSQLSERVER" not found. Check the name again...

The error occurs when installing SQL Server 2005 Developer Edition, SQL Server Express SP1, SQL Server Express SP2 CTR (with or without the SP2 Toolkit package installed beforehand). The error occurs with or without UAC.

The installation then fails. Please advise if you have any insights. SQL Server Express SP2 CTR was announced as a workable version for Vista... note that this is not the case.

I am just stating that I have the same problem.

|||

This is a problem on Vista if case sensitive collation is chosen and Windows computer name includes lower case characters.

Possible workarounds:

1. Change the computer name with upper case.

Since Vista does not allow to change a computer name to the same name with only case difference, this workaround requires two steps, changing to the different name first (ComputerName to ComputerNameX for example) and then changing to the original name with upper case (ComputerNameX -> COMPUTERNAME).

2. Change the collation that the customer's product uses from case sensitive (including binary) to case insensitive.

|||

Well thanks. That has worked

Microsoft really must make this a little more public so other people don't jump in this hole

|||

Some one at Microsoft connect has just confirmed that this is a known error.

quote "Also there is a known issue with install SP2 on Vista machines where the Machine name has lower case letters or other 'special' characters and you are using the non-default collation "

In fact, as we know, its a propblem with the install whatever service pack.

|||Milos,

Thank you. That worked correctly.

Considering the time that has been and is likely to continue to be frustratingly wasted by a great number of people, I agree that this mixed computer name case issue should be better documented. If only I could get the past 2 days of my life back.

Thanks again.|||SQL Server 2005 SP2 isn't released yet, and Microsoft has stated (repeatedly) that non-SP2 installs are not supported on Vista.|||

No, in fact Microsoft state that SQL Server 2005 is not supported on Vista without SP2.

I had downloaded the beta release of the service pack ready to apply but in order to apply the service pack, guess what? - you have to install the base version of the software!

So next time think before you make unhelpful and supercilious remarks.

|||

Understood - I think we're saying the same thing.

Also, it should be noted that you can *install* the software, it just isn't *supported* without SP2. That's because there are some changes in SP2 that make it work properly within the environment. Yes, you will still have to install the base package.

You'll notice in the readme file that comes with SP2 that it will have specific instructions for Vista installs, which is why I made these comments - which I think are both helpful and non-supercillious. No harm intended, I think you misunderstood my post.

|||Thank you for your comments. I could never get SQL Server 2005 installed on VISTA in order to apply the SP2. The setup would crash near the very end of the base installation as the SQL Server Native configuration string update could not discriminate between mixed case computer names when binary sort order was selected.

This was a very difficult problem to work through as the primary documentation discussing SQL Server and Vista stated that SQL Server SP2 was required. However, to apply SQL Server SP2 you had to get SQL Server installed. Thus, the catch 22 for those who were trying to install SQL Server 2005 using the new binary sort order option.

Right now, it seems that many of the bug fixes are found only by posting to newsgroups or forums such as this. People at Microsoft knew of this particular binary mixed computer name configuration string error and were likely fixing this in SP2, etc. However, the public didn't and thus we spent days of wasted frustrated time simply to get an error at the very end of the SQL Server setup procedure. Wouldn't it make sense for Microsoft to add on to the MSDN knowledge base "bug snippets" such as found in this forum itself. So instead of having days of human life wasted in installation frustration, one could do a search in MSDN online for the error message that I posted above, and the solution (as found above by the kind person) would be presented?|||

I hear you. I've spent lots of time on things only to find out later that someone had the info to help me all along! I think in Microsoft's defense that they haven't released patches for this issue yet, so they are working on not having to document them. If it turns out that you have to "work your way around" something, we want to make sure that we document it correctly, in the 9 languages we support, and subject to the legal and other rules we face in hundreds of countries around the world, and then test on the thousands of systems (SAP, custom apps, clustering, PDA's, replication, etc.) that we run on. That takes time, which is why we're asking for patience as we work through the issues.

The danger of posting something before we are done working on it is that it might "live" after the correct procedure is developed when the product is actually supported on Vista. Then we run into the problem of people possibly damaging their systems using a workaround for a problem we've corrected another way. So in effect, we're kind of in a catch-22 as well!

Luckily, Microsoft hosts these forums for exactly this reason. It give all of us DBAs a chance to hash this out in an informal setting, and helps the company feel the pain points of its customers. This lets us fix the problems before we support the product. These posts are VERY valuable, and we thank you all for making them. We're here to help.

|||

The funny part of this is that the day you posted this complaint is the same day Microsoft published the KB article on the topic.

http://support.microsoft.com/kb/929105 (Yes, it is about express but the concept is the same)

Chill out.. Microsoft is not some conglomerate conspiracy trying to screw the people that use thier software. That would be counter intuitive.

Since people are so trigger happy to sue the *** out of Microsoft whenever they misspell a word or misstate a concept it takes them time to edit/approve/audit the items that are published. Its the price of being a large company.

-David Sandor

|||This worked after changing the computer name to all caps (very offensive) and removing non-standard characters (like Underscore) when installed a case senitive collations are used. Of course I like to use things like Spaces in my tables and procedures! I would like to be able to use spaces in computer names as well, but then I just name the computer after what it is. I was finally able to get the software to install.|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - loke me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - like me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

Error installing SQL Server 2005 editions on Windows VISTA

There are numerous posts regarding this error when installing SQL Server 2005 on Windows Vista RTM thus I am starting a new thread in order to get resolution one way or another:

SQL Server Setup failed to execute a command for server configuration. The error was [SQL Native Client]Windows user or group "\USERNAME\SQLServer2005MSFTEUser$USERNAME$MSSQLSERVER" not found. Check the name again...

The error occurs when installing SQL Server 2005 Developer Edition, SQL Server Express SP1, SQL Server Express SP2 CTR (with or without the SP2 Toolkit package installed beforehand). The error occurs with or without UAC.

The installation then fails. Please advise if you have any insights. SQL Server Express SP2 CTR was announced as a workable version for Vista... note that this is not the case.

I am just stating that I have the same problem.

|||

This is a problem on Vista if case sensitive collation is chosen and Windows computer name includes lower case characters.

Possible workarounds:

1. Change the computer name with upper case.

Since Vista does not allow to change a computer name to the same name with only case difference, this workaround requires two steps, changing to the different name first (ComputerName to ComputerNameX for example) and then changing to the original name with upper case (ComputerNameX -> COMPUTERNAME).

2. Change the collation that the customer's product uses from case sensitive (including binary) to case insensitive.

|||

Well thanks. That has worked

Microsoft really must make this a little more public so other people don't jump in this hole

|||

Some one at Microsoft connect has just confirmed that this is a known error.

quote "Also there is a known issue with install SP2 on Vista machines where the Machine name has lower case letters or other 'special' characters and you are using the non-default collation "

In fact, as we know, its a propblem with the install whatever service pack.

|||Milos,

Thank you. That worked correctly.

Considering the time that has been and is likely to continue to be frustratingly wasted by a great number of people, I agree that this mixed computer name case issue should be better documented. If only I could get the past 2 days of my life back.

Thanks again.

|||SQL Server 2005 SP2 isn't released yet, and Microsoft has stated (repeatedly) that non-SP2 installs are not supported on Vista.|||

No, in fact Microsoft state that SQL Server 2005 is not supported on Vista without SP2.

I had downloaded the beta release of the service pack ready to apply but in order to apply the service pack, guess what? - you have to install the base version of the software!

So next time think before you make unhelpful and supercilious remarks.

|||

Understood - I think we're saying the same thing.

Also, it should be noted that you can *install* the software, it just isn't *supported* without SP2. That's because there are some changes in SP2 that make it work properly within the environment. Yes, you will still have to install the base package.

You'll notice in the readme file that comes with SP2 that it will have specific instructions for Vista installs, which is why I made these comments - which I think are both helpful and non-supercillious. No harm intended, I think you misunderstood my post.

|||Thank you for your comments. I could never get SQL Server 2005 installed on VISTA in order to apply the SP2. The setup would crash near the very end of the base installation as the SQL Server Native configuration string update could not discriminate between mixed case computer names when binary sort order was selected.

This was a very difficult problem to work through as the primary documentation discussing SQL Server and Vista stated that SQL Server SP2 was required. However, to apply SQL Server SP2 you had to get SQL Server installed. Thus, the catch 22 for those who were trying to install SQL Server 2005 using the new binary sort order option.

Right now, it seems that many of the bug fixes are found only by posting to newsgroups or forums such as this. People at Microsoft knew of this particular binary mixed computer name configuration string error and were likely fixing this in SP2, etc. However, the public didn't and thus we spent days of wasted frustrated time simply to get an error at the very end of the SQL Server setup procedure. Wouldn't it make sense for Microsoft to add on to the MSDN knowledge base "bug snippets" such as found in this forum itself. So instead of having days of human life wasted in installation frustration, one could do a search in MSDN online for the error message that I posted above, and the solution (as found above by the kind person) would be presented?

|||

I hear you. I've spent lots of time on things only to find out later that someone had the info to help me all along! I think in Microsoft's defense that they haven't released patches for this issue yet, so they are working on not having to document them. If it turns out that you have to "work your way around" something, we want to make sure that we document it correctly, in the 9 languages we support, and subject to the legal and other rules we face in hundreds of countries around the world, and then test on the thousands of systems (SAP, custom apps, clustering, PDA's, replication, etc.) that we run on. That takes time, which is why we're asking for patience as we work through the issues.

The danger of posting something before we are done working on it is that it might "live" after the correct procedure is developed when the product is actually supported on Vista. Then we run into the problem of people possibly damaging their systems using a workaround for a problem we've corrected another way. So in effect, we're kind of in a catch-22 as well!

Luckily, Microsoft hosts these forums for exactly this reason. It give all of us DBAs a chance to hash this out in an informal setting, and helps the company feel the pain points of its customers. This lets us fix the problems before we support the product. These posts are VERY valuable, and we thank you all for making them. We're here to help.

|||

The funny part of this is that the day you posted this complaint is the same day Microsoft published the KB article on the topic.

http://support.microsoft.com/kb/929105 (Yes, it is about express but the concept is the same)

Chill out.. Microsoft is not some conglomerate conspiracy trying to screw the people that use thier software. That would be counter intuitive.

Since people are so trigger happy to sue the *** out of Microsoft whenever they misspell a word or misstate a concept it takes them time to edit/approve/audit the items that are published. Its the price of being a large company.

-David Sandor

|||This worked after changing the computer name to all caps (very offensive) and removing non-standard characters (like Underscore) when installed a case senitive collations are used. Of course I like to use things like Spaces in my tables and procedures! I would like to be able to use spaces in computer names as well, but then I just name the computer after what it is. I was finally able to get the software to install.|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - loke me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

|||

Hi every body,

I have also the same problem.

Perhaps what you said is the solution, but I think that the persons - like me- who have windows vista must first get the "Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 "

on this web adress http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5b5528b9-13e1-4db9-a3fc-82116d598c3d

I'm working on it right now.. And I hope that will resolve my problems.

Any way If I know that Vista is - for the moment - so in his own glob like a mystic person - I would never buy it...!

Sincerely,

RAF

sql

Error Importing using vista a comma deliminated file

I find I can sucessfully input a tab deliminated file but not a comma deliminated file.

I have installed all patches and have administrator access to my computer.

I am using Windows Vista. The input file is app 3 GB

When I let SQL Server 2005 create a new table from the import I receive the error

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Success)

- Prepare for Execute (Success)

- Pre-execute (Success)

Messages

Information 0x402090dc: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has started.
(SQL Server Import and Export Wizard)

- Executing (Success)

- Copying to [VoterRecords].[dbo].[Skinner-VOTERLIST-12-MAR-07rev2] (Error)

Messages

Error 0xc02020a1: Data Flow Task: Data conversion failed. The data conversion for column "Column 32" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
(SQL Server Import and Export Wizard)

Error 0xc020902a: Data Flow Task: The "output column "Column 32" (138)" failed because truncation occurred, and the truncation row disposition on "output column "Column 32" (138)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
(SQL Server Import and Export Wizard)

Error 0xc0202092: Data Flow Task: An error occurred while processing file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" on data row 38643.
(SQL Server Import and Export Wizard)

Error 0xc0047038: Data Flow Task: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) returned error code 0xC0202092. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)

Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.
(SQL Server Import and Export Wizard)

Error 0xc0047039: Data Flow Task: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled.
(SQL Server Import and Export Wizard)

Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited.
(SQL Server Import and Export Wizard)

- Post-execute (Success)

Messages

Information 0x402090dd: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has ended.
(SQL Server Import and Export Wizard)

Information 0x402090df: Data Flow Task: The final commit for the data insertion has started.
(SQL Server Import and Export Wizard)

Information 0x402090e0: Data Flow Task: The final commit for the data insertion has ended.
(SQL Server Import and Export Wizard)

- Cleanup (Success)

Messages

Information 0x4004300b: Data Flow Task: "component "Destination - Skinner-VOTERLIST-12-MAR-07rev2" (186)" wrote 30366 rows.
(SQL Server Import and Export Wizard)

When I import into a pre created table where all fields are set to varchar(255)

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Warning)

Messages

Warning 0x80047076: Data Flow Task: The output column "Column 0" (10) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 1" (14) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 2" (18) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 3" (22) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 4" (26) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 5" (30) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 6" (34) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 7" (38) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 8" (42) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 9" (46) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 10" (50) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 11" (54) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 12" (58) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 13" (62) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 14" (66) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 15" (70) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 16" (74) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 17" (78) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 18" (82) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 19" (86) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 20" (90) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 21" (94) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 22" (98) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 23" (102) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 24" (106) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 25" (110) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 26" (114) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 27" (118) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 28" (122) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 29" (126) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 30" (130) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 31" (134) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 32" (138) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 33" (142) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 34" (146) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 35" (150) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 36" (154) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 37" (158) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 38" (162) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 39" (166) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 40" (170) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 41" (174) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 42" (178) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 43" (182) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 0" (10) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 1" (14) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 2" (18) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 3" (22) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 4" (26) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 5" (30) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 6" (34) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 7" (38) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 8" (42) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 9" (46) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 10" (50) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 11" (54) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 12" (58) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 13" (62) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 14" (66) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 15" (70) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 16" (74) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 17" (78) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 18" (82) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 19" (86) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 20" (90) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 21" (94) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 22" (98) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 23" (102) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 24" (106) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 25" (110) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 26" (114) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 27" (118) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 28" (122) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 29" (126) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 30" (130) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 31" (134) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 32" (138) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 33" (142) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 34" (146) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 35" (150) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 36" (154) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 37" (158) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 38" (162) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 39" (166) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 40" (170) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 41" (174) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 42" (178) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 43" (182) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

- Prepare for Execute (Success)

- Pre-execute (Error)

Messages

Information 0x402090dc: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has started.
(SQL Server Import and Export Wizard)

Error 0xc0202004: Data Flow Task: The number of columns is incorrect.
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - fl_voter_history" (186) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)

- Executing (Success)

- Copying to [VoterRecords].[dbo].[fl_voter_history] (Stopped)

- Post-execute (Stopped)

Messages

Information 0x402090dd: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has ended.
(SQL Server Import and Export Wizard)

- Cleanup (Success)

Messages

Information 0x4004300b: Data Flow Task: "component "Destination - fl_voter_history" (186)" wrote 0 rows.
(SQL Server Import and Export Wizard)

I find I can sucessfully input a tab deliminated file but not a comma deliminated file.

I have installed all patches and have administrator access to my computer.

I am using Windows Vista. The input file is app 3 GB

When I let SQL Server 2005 create a new table from the import I receive the error

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Success)

- Prepare for Execute (Success)

- Pre-execute (Success)

Messages

Information 0x402090dc: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has started.
(SQL Server Import and Export Wizard)

- Executing (Success)

- Copying to [VoterRecords].[dbo].[Skinner-VOTERLIST-12-MAR-07rev2] (Error)

Messages

Error 0xc02020a1: Data Flow Task: Data conversion failed. The data conversion for column "Column 32" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
(SQL Server Import and Export Wizard)

Error 0xc020902a: Data Flow Task: The "output column "Column 32" (138)" failed because truncation occurred, and the truncation row disposition on "output column "Column 32" (138)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
(SQL Server Import and Export Wizard)

Error 0xc0202092: Data Flow Task: An error occurred while processing file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" on data row 38643.
(SQL Server Import and Export Wizard)

Error 0xc0047038: Data Flow Task: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) returned error code 0xC0202092. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)

Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.
(SQL Server Import and Export Wizard)

Error 0xc0047039: Data Flow Task: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled.
(SQL Server Import and Export Wizard)

Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited.
(SQL Server Import and Export Wizard)

- Post-execute (Success)

Messages

Information 0x402090dd: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has ended.
(SQL Server Import and Export Wizard)

Information 0x402090df: Data Flow Task: The final commit for the data insertion has started.
(SQL Server Import and Export Wizard)

Information 0x402090e0: Data Flow Task: The final commit for the data insertion has ended.
(SQL Server Import and Export Wizard)

- Cleanup (Success)

Messages

Information 0x4004300b: Data Flow Task: "component "Destination - Skinner-VOTERLIST-12-MAR-07rev2" (186)" wrote 30366 rows.
(SQL Server Import and Export Wizard)

When I import into a pre created table where all fields are set to varchar(255)

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Warning)

Messages

Warning 0x80047076: Data Flow Task: The output column "Column 0" (10) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 1" (14) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 2" (18) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 3" (22) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 4" (26) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 5" (30) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 6" (34) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 7" (38) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 8" (42) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 9" (46) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 10" (50) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 11" (54) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 12" (58) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 13" (62) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 14" (66) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 15" (70) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 16" (74) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 17" (78) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 18" (82) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 19" (86) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 20" (90) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 21" (94) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 22" (98) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 23" (102) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 24" (106) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 25" (110) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 26" (114) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 27" (118) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 28" (122) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 29" (126) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 30" (130) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 31" (134) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 32" (138) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 33" (142) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 34" (146) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 35" (150) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 36" (154) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 37" (158) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 38" (162) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 39" (166) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 40" (170) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 41" (174) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 42" (178) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 43" (182) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 0" (10) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 1" (14) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 2" (18) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 3" (22) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 4" (26) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 5" (30) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 6" (34) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 7" (38) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 8" (42) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 9" (46) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 10" (50) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 11" (54) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 12" (58) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 13" (62) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 14" (66) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 15" (70) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 16" (74) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 17" (78) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 18" (82) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 19" (86) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 20" (90) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 21" (94) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 22" (98) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 23" (102) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 24" (106) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 25" (110) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 26" (114) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 27" (118) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 28" (122) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 29" (126) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 30" (130) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 31" (134) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 32" (138) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 33" (142) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 34" (146) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 35" (150) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 36" (154) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 37" (158) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 38" (162) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 39" (166) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 40" (170) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 41" (174) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 42" (178) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

Warning 0x80047076: Data Flow Task: The output column "Column 43" (182) on output "Flat File Source Output" (2) and component "Source - Skinner-VOTERLIST-12-MAR-07rev2_TXT" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

- Prepare for Execute (Success)

- Pre-execute (Error)

Messages

Information 0x402090dc: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has started.
(SQL Server Import and Export Wizard)

Error 0xc0202004: Data Flow Task: The number of columns is incorrect.
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - fl_voter_history" (186) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)

- Executing (Success)

- Copying to [VoterRecords].[dbo].[fl_voter_history] (Stopped)

- Post-execute (Stopped)

Messages

Information 0x402090dd: Data Flow Task: The processing of file "C:\NYData\Skinner-VOTERLIST-12-MAR-07rev2.TXT" has ended.
(SQL Server Import and Export Wizard)

- Cleanup (Success)

Messages

Information 0x4004300b: Data Flow Task: "component "Destination - fl_voter_history" (186)" wrote 0 rows.
(SQL Server Import and Export Wizard)

|||Can you try removing some rows from the file to make the size smaller and see if that works?|||

michaelh613 wrote:

I find I can sucessfully input a tab deliminated file but not a comma deliminated file.

My guess is there's a comma in the data that is throwing off the parser.
|||Is there any tool that I can use in SQL server to determine where the error is occurring. You may be correct about the , but I am at a loss how to find it|||

You can try saving the package and then setting to redirect rows on truncation in flat file source.

HTH.