| Author |
DTS Package fails when importing Excel sheet
|
|
|
| Arghhh......the inconsistencies of Microsoft. We have to live with them
don't we?
I have an Excel file.
I created a package to import it into a SQL server database table. I run it
from my machine's SQL Enterprise manager...it runs great
I log into the server
Run it from Enterprise manager. It fails miserably. Error? "....conversion
invalid for data types on column pair 1 (source column 'F6' (dbtype_wstr)
destination column change$ (dbtype_R8)
I have tried everything. No luck
Why? Please someone tell me why would the DTS run from my machine and not
from the server? There's no specific installation configuration differences
between the two. The only difference is that I have excel installed on my
machine. I hope that doesn't mean I have to install office on the server
because that is not going to happen.
Help! Please!
Regards,
Leo
| |
|
| Damn it. Found the solution...on my own of course since there's no MS help
for that anywhere. I did have to modify the registry. The only way to get it
to work. But it works as it is supposed to now.........
"Leo" <none@none.com> wrote in message
news:e39GjicJGHA.2708@tk2msftngp13.phx.gbl...
> Arghhh......the inconsistencies of Microsoft. We have to live with them
> don't we?
>
> I have an Excel file.
>
> I created a package to import it into a SQL server database table. I run
it
> from my machine's SQL Enterprise manager...it runs great
>
> I log into the server
>
> Run it from Enterprise manager. It fails miserably. Error? "....conversion
> invalid for data types on column pair 1 (source column 'F6' (dbtype_wstr)
> destination column change$ (dbtype_R8)
>
> I have tried everything. No luck
>
> Why? Please someone tell me why would the DTS run from my machine and not
> from the server? There's no specific installation configuration
differences
> between the two. The only difference is that I have excel installed on my
> machine. I hope that doesn't mean I have to install office on the server
> because that is not going to happen.
>
> Help! Please!
>
> Regards,
> Leo
>
>
>
| |
| Allan Mitchell 2006-01-30, 8:24 pm |
| Hello Leo,
What part of the registry did you have to change?
You do not need to install Excel on the server as the ability to use Excel
as a source and a destination is taken care of by MDAC.
Allan
[color=darkred]
> Damn it. Found the solution...on my own of course since there's no MS
> help for that anywhere. I did have to modify the registry. The only
> way to get it to work. But it works as it is supposed to now.........
>
> "Leo" <none@none.com> wrote in message
> news:e39GjicJGHA.2708@tk2msftngp13.phx.gbl...
> it
>
> differences
>
| |
| Francois Malgreve 2006-01-31, 7:23 am |
| There is a tweak that most people have to do , it's to set the key
'TypeGuessRows' under the registry path
HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Je
t\4.0\Engines\Excel to 0
more info on:
http://support.microsoft.com/?kbid=281517
Is it what you did, Leo?
Francois
"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:f0343b03125508c
7f401778178b0@msnews
.microsoft.com...
> Hello Leo,
>
> What part of the registry did you have to change?
>
> You do not need to install Excel on the server as the ability to use Excel
> as a source and a destination is taken care of by MDAC.
>
>
> Allan
>
>
>
| |
| Allan Mitchell 2006-01-31, 7:23 am |
| Hello Francois,
That is what I was wondering also. It is one of the reasons we wrote this
article
Excel Inserts Null Values
(http://www.sqldts.com/default.aspx?254)
Allan
[color=darkred]
> There is a tweak that most people have to do , it's to set the key
> 'TypeGuessRows' under the registry path
> HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Je
t\4.0\Engines\Excel to 0
>
> more info on:
>
> http://support.microsoft.com/?kbid=281517
>
> Is it what you did, Leo?
>
> Francois
>
> "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:f0343b03125508c
7f401778178b0@msnews
.microsoft.com...
>
|
|
|
|