Alrighty Here is what I did
I set up the DSN and don't think it has been changed but I will work through it and see what is different. Ran it in the Query Analyser on the Test box worked fine, ran it in the Enterprise manager on the test box worked fine. Took out the datatype and it still throws the same error. Just to make things more interesting this was working up to a while ago and I don't know what has changed. Thanks Niall -----Original Message----- From: Jonah Simpson [mailto:[EMAIL PROTECTED] Sent: 04 November 2003 09:30 To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Error: Invalid character value for cast specification Hey Niall! Weird error dude! I can't see anything wrong with your code...but it IS late here. ; > The only thing I can think of is that for some reason the data being returned to you is in the form of a string or something. Try this: <@BIND NAME="local$uniqueName" bindtype="out"> And see if its outputting the proper datatype/data. Have you tried running the stored procedure in just the SQL editor for (I'm guessing) SQL Server ? You said it works on your dev server but not your test server? Same datasource? Same configurations and versions for your ODBC drivers? These are the only things I can think of mang. Good luck and let us know what the solution to your problem is! Jonah Simpson ----- Original Message ----- From: "Niall Merrigan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 04, 2003 1:50 AM Subject: Witango-Talk: Error: Invalid character value for cast specification Hi folks This error has just seemed to pop up. I copied the offending DBMS action out to a test file in case it was an error somewhere else in the original taf but it replicates. TAF File: /idocs/test.taf Position: call_spGetUniqueFilename Class: DBMS Error Number: 0 Description: [Microsoft][ODBC SQL Server Driver]Invalid character value for cast specification TAF File: /idocs/test.taf Position: call_spGetUniqueFilename Class: Internal Error Number: -101 Description: General error during data source operation. I have a Direct DBMS action which calls the following {call spGetUniqueFileName( <@BIND NAME=uniqueName BINDTYPE=OUT DATATYPE=INTEGER SCOPE=LOCAL> )} The SQL SP it calls is the following /****** Object: Stored Procedure dbo.spGetUniqueFileName Script Date: 30/07/2002 14:48:10 ******/ CREATE Procedure spGetUniqueFileName @UniqueName int OUTPUT AS begin tran -- transaction used to ensure only one process at a time does this select @UniqueName = (fldFileName+1) from tblFileNameGen update tblFileNameGen set fldFileName = @UniqueName commit tran return (@UniqueName) GO The field its reading and updating is a NON NULL field INT(4) with a value currently of 389. The thing it works fine on the dev server and this is the test server that is causing the issue. Any ideas Thanks Niall ******************************************************************** This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed. It may contain information which is privileged and confidential within the meaning of applicable law. If you are not the intended recipient, please contact the sender as soon as possible. The views expressed in this communication may not necessarily be the views held by LGCSB (Local Government Computer Services Board). Any attachments have been checked by a virus scanner and appear to be clean. Please ensure that you also scan all messages, as LGCSB does not accept any liability for contamination or damage to your systems. ******************************************************************** ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ******************************************************************** This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed. It may contain information which is privileged and confidential within the meaning of applicable law. If you are not the intended recipient, please contact the sender as soon as possible. The views expressed in this communication may not necessarily be the views held by LGCSB (Local Government Computer Services Board). Any attachments have been checked by a virus scanner and appear to be clean. Please ensure that you also scan all messages, as LGCSB does not accept any liability for contamination or damage to your systems. ******************************************************************** ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
