May 21, 2012 at 5:03 am
Hi,
I was trying to create a table by importing an excel sheet through the import/export wizard.
Im ending up getting the following 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 (Stopped)
- Pre-execute (Stopped)
- Executing (Error)
Messages
Error 0xc002f210: Preparation SQL Task 1: Executing the query "CREATE TABLE [dbo].[Sheet1$] (
[ID] float,
[Name..." failed with the following error: "profile name is not valid". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
(SQL Server Import and Export Wizard)
- Copying to [dbo].[Sheet1$] (Stopped)
- Post-execute (Stopped)
I guess there is a problem with the db mail i have configured. not sure though.
Thanks in advance 🙂 !
May 21, 2012 at 5:28 am
why would dbmail be an issue in an import routine?
does the table $Sheet1 get created? if so does it need to be deleted before you can run the import?
is it being created with the right data types? - excel is notorious for this
MVDBA
May 21, 2012 at 6:06 am
michael vessey (5/21/2012)
why would dbmail be an issue in an import routine?does the table $Sheet1 get created? if so does it need to be deleted before you can run the import?
is it being created with the right data types? - excel is notorious for this
The Sheet is not getting created, i guess that is what the error says. The CREATE TABLE is failing saying that "profile name is not valid".
AS far as the datatypes are concerned , i are fine too.
excel :
IDNameAdress
1Harrypal1Mumbai1
2Harrypal2Mumbai2
3Harrypal3Mumbai3
4Harrypal4Mumbai4
datatypes :
float nvarchar nvarchar
the
May 21, 2012 at 6:33 am
well the float data type definatly looks wrong to me - int looks better, but that is beside the point.
have you closed the excel file correctly before you run the import? you can't have the file open when you run the import
MVDBA
May 21, 2012 at 9:54 am
You are right , int would certainly look better, but float should work too , right ?
and yes , the names right , its saved as .xls and its not open or in use.
Just FYI , Im using the Developer Edition , that shouldnt be a problem too i guess.
Whats with the error though ? Profile name not valid . Does that point to anything .
I dread the thought that im missing out on something silly here, but i have a nasty feeling thats tha case herer 🙁 🙁 !
May 21, 2012 at 10:08 am
I think the use of the word profile in the error might be relating to some jet 4 components.
if you only need to import this data once then you could just create the table yourself and then highlight it in excel and copy / paste straight into management studio.
MVDBA
May 22, 2012 at 5:41 am
There is a really strange issue going on here Mike.
I tried to create the table first as u said through GUI , but yet again it gives me the profile name error !?
ERROR :::
'Table_1' table
- Unable to create table.
you are not allowed to alter the Table
profile name is not valid
The transaction ended in the trigger. The batch has been aborted.
That prompted me to check out with the Security level. And guess what , the login i am using is a db_owner for the database.
FYI , i had brought up this db by restoring an archived backup from a different server.
My login was not mapped to the db , so i mapped it and gave it db_owner rights.
So is the error a security related issue ?
May 22, 2012 at 5:59 am
'Table_1' table
- Unable to create table.
you are not allowed to alter the Table
profile name is not valid
The transaction ended in the trigger. The batch has been aborted.
this is being caused by a DDL trigger - a database trigger is preventing you from creating a new table
this must have been coded into the database by a developer or DBA - possibly they check who you are logged in as then ROLL BACK the create table statement if you aren't the right "Profile"
MVDBA
May 22, 2012 at 6:01 am
i used to do this to prevent my devs running as "SA" - we were required to audit schema changes , so if an object was modified by "SA" then we rolled it back and forced them to use NT Authentication - something similar is happening here
MVDBA
May 22, 2012 at 9:09 am
Right , i guess that is what the problem is , cause creating a similar table in another database similarly restored isnt giving me the error.
Smart DBA huh? who ever put that rollback thing into place ! 😀
Thanks a lot for your help Mike 🙂
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply