Hi all,
Has anyone ever received the following error in the Ticket Import Utility - Import Process Log output? : "Error 0, Severity 0, State 0, Procedure , Line 0, "
The rest of the output details the parameters in my import set so I'm guessing this is a configuration issue or a problem with my file path. I'm in Test and we are on RAMP so the current filepath in my import set is: "\\kriostess\pub\NYCO\Test\User_Reports\Imports\"
I ran a trace while running the import in Test and the only lead I see is at the bottom -Object Name - TP_ORDER_IMPORT_MAINTextData - Set @error_message = 'Order solicitor/userid (' + convert(varchar, @default_solicitor) + ') is not valid.'
But this error doesn't actually spit out anywhere, and Order Solicitor is not a parameter in the Import Set so I'm not sure how it's related.
Anyone seen this?
Frannie
Looks to me like you have a NULL solicitor field in TR_IMPORT_ORDER_SET.solicitor, which unfortunately we don’t enforce to have a value when saving from System Tables. The error message appears to be showing up as blank because the solicitor value is NULL and the error log message isn’t being produced correctly. This is logged as a defect and will be corrected in v12 and/or another v11 maintenance release.
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Frances O'Connell Sent: Thursday, January 10, 2013 4:06 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Order Import Error
I ran a trace while running the import in Test and the only lead I see is at the bottom - Object Name - TP_ORDER_IMPORT_MAIN TextData - Set @error_message = 'Order solicitor/userid (' + convert(varchar, @default_solicitor) + ') is not valid.'
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thank you Ryan. This makes sense and in our v.11 Test environment I filled in the TR_IMPORT_ORDER_SET.solicitor field and the import log moved on (to the next XML error, but that's another story :).
However in our Live environment which is still v.10, the drop down in the TR_IMPORT_ORDER_SET. system table does not have any values available in the solicitor column. Same error in Trace in Live too: "Set @error_message = 'Order solicitor/userid (' + convert(varchar, @default_solicitor) + ') is not valid.'"
The column properties look the same from Test to Live in SSMS. Is there any reason this would be happening in 10 and not 11? Or Live and not Test?
Thanks all -
Hi all (and Ryan),
Found another thread discussing this problem in v.10 - http://www.tessituranetwork.com/Community/forums/t/6159.aspx. Looks like the solution is there!
Thanks!