Odbc Error Invalid Parameter Number
Contents |
belongs to an external system out of the direct control of this product team. A more detailed explanation for excel sql invalid parameter number the resolution of this particular item may have been provided in
Excel Invalid Parameter Number Invalid Descriptor Index
the comments section. 8 1 Sign into vote ID 683858 Comments 7 Status Closed Workarounds 0 Type microsoft odbc sql server driver invalid descriptor index Bug Repros 8 Opened 8/11/2011 9:14:22 AM Access Restriction Public Description Using MS Query to connect to MS SQL Server 2005 as a workaround to pass parameters. excel 2013 invalid parameter number When changing SQL statement in the Command Text to contain a ? (question mark) as a placeholder for a parameter, getting two message boxes in sequence with the following errors: [Microsoft][ODBC SQL Server Driver]Invalid Parameter Number [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index This only happens when the SQL statement cannot be represented graphically, e.g. in my case it contains
Excel Invalid Descriptor Index
a CTE. Simple queries (e.g. SELECT column1 FROM table1 WHERE column2 = ?) do not generate this error, but execute OK. The behaviour was reported in the forums (http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/99e25a59-9df7-41f1-9032-3fe454326d32) and acknowledged by a MS rep to be a problem, but I could not find any bug reports for this. DETAILS ATTACH A FILE EDIT THIS ITEM Assign To Item can only be reassigned when it is active. Comments (7) | Workarounds (0) | Attachments (0) Sign in to post a comment. Please enter a comment. Submit Posted by mjs128 on 10/12/2016 at 12:49 PM This is still a bug. See example query select b.EV_EVNM as [Event Name], c.ET_EVENT_TYPE_CODE as [Event Type], b.EV_START_DATE as [Event Start Date], b.EV_END_DATE as [Event End Date], a.LN_DISPLAY_NAME as [Zone], a.RT_RESOURCE_TYPE as [Resource Type], a.EV_EVENT_ID as [Event ID], a.Resources_Requested as [Number of Resources]from (select a.RT_RESOURCE_TYPE, a.EV_EVENT_ID, c.LN_DISPLAY_NAME,SUM(a.TR_REQUESTED_COUNT) as Resources_Requestedfrom [ERM].[dbo].TR_TEAM_RESOURCE a left join [ERM].[dbo].RV_EVENT_TEAM b on (a.RV_GROUP_ID = b.RV_GROUP_ID AND a.EV_EVENT_ID = b.EV_EVENT_ID)left join [ERM].[dbo].LN_LOCATION c on b.LN_LOCATION_NAME = c.LN_LOCATION_NAMEwhere (c.LN_DISPLAY_NAME like '%unassigned%')group
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta odbc invalid parameter number Discuss the workings and policies of this site About Us Learn excel odbc sql server driver invalid descriptor index more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack
Invalid Parameter Number. Sqlstate=s1093 Db2
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, https://connect.microsoft.com/SQLServer/feedback/details/683858/ helping each other. Join them; it only takes a minute: Sign up Invalid parameter number, SQL state S1093 php odbc mssql up vote 2 down vote favorite We have a uni student doing work experience at the moment and he's doing a Wordpress prototype for us (as we have neither Wordpress or PHP experience). It's running on http://stackoverflow.com/questions/17918459/invalid-parameter-number-sql-state-s1093-php-odbc-mssql a Windows server and while Wordpress itself is running in mySQL, as all our existing databases are in MS SQL Server 2005/2008 and he's trying to call a stored procedure in a php page using this code: $connection = odbc_connect('DB', 'UNAME', 'PWORD'); $request = odbc_prepare($connection, "CALL ProcName(?, ?, ?)"); if(!$request) die("Could not prepare statement:" . odbc_errormsg()); $result = odbc_execute($request, array("var1", "var2", "var3")); if(!$result) die("Could not execute statement:" . odbc_errormsg()); The stored procedure is like this: ROCEDURE [dbo].[ProcName] (@option1 varchar(50), @option2 varchar(50), @option3 varchar(50)) AS ... lots of logic end with... select * from tblName The stored procedure is used both by .net pages and Livelink CMS pages and works correctly but when we try to call it from php, it errors with: "odbc_execute(): SQL error: [Microsoft][ODBC SQL Server Driver]Invalid parameter number, SQL state S1093 in SQLDescribeParameter in C:\inetpub\wordpress\test.php on line 29" Strangely, if we rename the procedure call to a non existant stored procedure, it errors with exactly the same thing rather than a stored procedure cannot be found
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/10935516/php-odbc-stored-procedure-invalid-parameter-number hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. http://uneventech.blogspot.com/2012/08/odbc-sql-server-driver-invalid.html Join them; it only takes a minute: Sign up PHP ODBC Stored Procedure Invalid Parameter Number up vote 4 down vote favorite I am 100% brand new to this world of SQL/PHP/ODBC/FBI/TLA etc. so I apologize if what I invalid parameter am asking is incredibly basic. I am using a stored procedure that uses a lat/long database of zip codes to take a central zipcode and a given mile radius as 2 input parameters, and then returns an array of zip codes that are within that given mile radius. It works perfectly when I run it in my SQL viewer, but when I try to use php to do the same, I only get invalid parameter errors. $connstr = "Driver={SQL invalid parameter number Server};Server=MyServer;Database=MyDatabase;"; $conn = odbc_connect($connstr, "Name", "PW"); $query_string = " CALL FindZipCodeWithinRadius(?,?) "; $sp = odbc_prepare($conn, $query_string); $zipcodes = odbc_execute($sp,array(" 14602, 35")); print_r($zipcodes); When I run the code like this, I get the error "Not enough parameters (1 should be 2)" I have tried different iterations of double quotes/single quotes around those input parameters, but they all either give me the above error, or this error: "SQL error: [Microsoft][ODBC SQL Server Driver]Invalid parameter number, SQL state S1093" A quick google search leads me to believe that the second error means that there are far too many parameters being read in to the proc, so how did I go from 1 to many while skipping the desired 2? The database is on SQL 2000 if that makes a difference. Any ideas? Thanks for any help you can provide. php stored-procedures odbc share|improve this question asked Jun 7 '12 at 16:01 user1442631 212 Please post your stored procedure. We could be here all day guessing what it requires. Did you try array("14602", 35)? –Gordon Freeman Jan 5 '13 at 7:50 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote $zipcodes = odbc_execute($sp,array(" 14602, 35")); Should be $zipcodes = odbc_execute($sp,array("14602", "35")); In your execute you are passing 1 array value, " 14602, 35", and your prepared statement is looking for 2. share|improve this answer answered Jun 7 '12 at 16:08
you have to use "From Microsoft Query." This is the only external source that accepts parameters in Excel 2010. In the example above, I setup a connection properties to call a stored procedure with 3 parameters and I keep getting the "Invalid parameter number" error. As it turns out, the user doesn't have enough permission to execute the stored procedure but the error certainly misled me and wasted a lot of time on it. Posted by Sean T. at 7:01 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2016 (2) ► May (1) ► Jan (1) ► 2015 (80) ► Dec (52) ► May (1) ► Apr (1) ► Mar (10) ► Feb (1) ► Jan (15) ► 2013 (10) ► Nov (2) ► Jul (8) ▼ 2012 (7) ▼ Aug (1) MSSQL - [ODBC SQL Server Driver] invalid parameter... ► May (6) Simple template. Powered by Blogger.