Hello all!
I am trying to run the NCOA processing utility and am having lots of issues. I've got a TASK ticket open as well, but wanted to see if anyone else in the community had some advice. So I ran the export and sent off the data to Zeta Interactive and they sent me the import file back. The first time I tried to import, I received the error: "Report request cancelled due to a Datawindow Retrieval Error - Error code: 50000, Error Text: Select Error: SQLSTATE = 42000 Microsoft OLE DB Provider for SQL Server BCP failed: Unspecified BCP Error.
The response I got back from TASK was that since I edited the file in excel and the last column had no data in it, it would get cut off from the import. So I fixed the issue by adding a number to the last column of the file and then the import into Test worked fine, as did the processing. I then tried to import the same file into Live, but it popped back with that same "Unspecified BCP Error" that I got to begin with. There's definitely data in the last column so that's not the issue, but I have not a clue what is.
I've now tried importing a bunch of times with a bunch of files, and I can't even seem to import into Test anymore, always getting the same Unspecified BCP error no matter what. I've tried small files with 20 or even just only 1 record (including files that had imported before into Test no problem). I even tried just importing the txt file I got back from Zeta directly without doing any editing in Excel first just to see if that would work, and I still got the same error.
Anyone have any idea what I'm doing wrong or how to fix this?? We're on V15.03, and RAMP hosted if that makes any difference.
Thanks,
Sara
Hi Sara,
I recently went through a bit of an issue with importing a Zeta NCOA update as well. And i told them the problem with the last column so you'd think they'd have fixed it. But here are a couple of things to try:
First, you can get a more specific error code by using the SQL code:
select * from T_NCOA_Process_Log where ncoa_session = enter the number of your session
Also double check T_NCOA_SESSION where ncoa_session = enter the number of your session
If there's a date in the import_date column you should clear that out so it doesn't think you've already completed the import for that session.
There are a couple of other things but try getting the specific error code and checking for the import date first.
-Amanda
Hi Amanda,
I double checked T_NCOA_SESSION and there's no date in the import_date column, so good there. But I do see a couple interesting things in T_NCOA_PROCESS_LOG. So in Test I was getting errors because I was trying to import the same file multiple times and thus causing some duplicate key errors, so that makes sense. But looking at the logs in test, this error is what's popping up for all my import attempts:
Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Invalid object name '[dbo].TW_NCOA_INCOMING'.
Which doesn't make sense because that table definitely exists...
-Sara
Sara Broderick said:Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Invalid object name '[dbo].TW_NCOA_INCOMING'.
I haven't seen that one before. Definitely send it to TASK. Sorry, I can't be of more help.
You were a huge help pointing me to the T_NCOA_PROCESS_LOG table, thank you!