Microsoft odbc driver manager function sequence error

Not sure if directly related, but I am seeing the function sequence error appear randomly on different usage scenarios.

All of them when trying to iterate over a client buffered result set.

Hi david-garcia-garcia can you explain some of the usage scenarios that are causing the sequence error. I am with the team at Microsoft that own’s this driver. I might be able to help you out.

The case was too complex and would need investigation to really isolate the steps to reproduce. But it did share something similar with the sample script I provided in the same comment:

• The error came and go intermitently (one request with error, the next one without, and so on…)
• The error appeared after previous operations on the same connection dealt with failing transactions and rollbacks.

If you could get to reproduce the error with the provided script there’s a chance that both of them are indeed the same bug.

I am seeing this error consistently on Drupal 8 — MSSQL integration (and is preventing any further development because it breaks man automated tests…).

Unluckily, the circumstances that lead to the error are so complex that I was unsuccessfull at isolating a test script. I even tried to PROXY all operations on Drupal’s database abstraction layer to later reproduce every single operation done against the PDO driver without luck, the error simply won’t reproduce.

If you are interested in helping solve this out to get D8 working on MSSQL Server, I can provide the exact steps to reproduce on a clean D8 install. You will need the -dev version of the SQL Server driver for Drupal — that I can only share privately at the moment.

I’d love to take a look at this.

Can you share the repro steps and the dev version driver?

Thanks

From: Davvid [mailto:notifications@github.com]
Sent: Monday, July 20, 2015 6:36 AM
To: Azure/msphpsql
Subject: Re: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

I am seeing this error consistently on Drupal 8 — MSSQL integration (and is preventing any further development because it breaks man automated tests…).

Unluckily, the circumstances that lead to the error are so complex that I was unsuccessfull at isolating a test script. I even tried to PROXY all operations on Drupal’s database abstraction layer to later reproduce every single operation done against the PDO driver without luck, the error simply won’t reproduce.

If you are interested in helping solve this out to get D8 working on MSSQL Server, I can provide the exact steps to reproduce on a clean D8 install. You will need the -dev version of the SQL Server driver for Drupal — that I can only share privately at the moment.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-122886221.

Steps to reproduce:

• Download a fresh copy of D8: git clone —branch 8.0.x http://git.drupal.org/project/drupal.git
• Setup the site on IIS (see attached phpinfo() for enabled extensions and overal configuration)
• Unzip the SQL Server driver to the root of drupal, this will show you SQL Server as an available target during the install process.
• Install on SQL Server
• Go to /admin/modules and enable the «testing» module
• Go to /admin/config/development/testing and enable the DrupalsearchTestsSearchNumbersTest inside the «Search» group.
• Set a breakpoint in line 183 of coremodulesdblogsrcControllerDbLogController.php (this is the loop where the error happens)
• Run Tests. When the breakpoint is hit use F10 (Visual Studio + PHP Tools to debug) to step through about 4 times, the exception is thrown.

I found out that completely removing transaction management from the Drupal driver prevents the error from happening.

https://drive.google.com/file/d/0B2bjxiZ1Bb4BZmxNWnd1YmFpdDg/view?usp=sharing

(zip with sqlsrv driver, phpinfo() dump and screenshot of the exception)

Good luck. At least the exception is consistently reproducible.

Greetings

Any luck with this? D8 is to be released before the end of the year, it would be nice to have it working on MSSQL shortly before that happens.

I’m looking into it. I’ll,keep you posted on that. Give me a week, since I was out of town.

Thanks

Sent from my iPad

On Aug 4, 2015, at 11:03 PM, Davvid <notifications@github.commailto:notifications@github.com> wrote:

Any luck with this? D8 is to be released before the end of the year, it would be nice to have it working on MSSQL shortly before that happens.

Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-127882620.

Do not use the latest D8 HEAD, download something from the date of my original post. Recent changes in D8 have broken the MSSQL driver for Drupal.

When I’m trying to create the SQL Server database in Drupal 8, I’m getting the following error in the PHP56 error_log file:

[11-Aug-2015 22:04:27 America/Los_Angeles] PHP Fatal error: Call to undefined function DrupalDriverDatabasesqlsrvwincache_ucache_get() in C:inetpubwwwrootdrupaldriverslibDrupalDriverDatabasesqlsrvConnection.php on line 607

Any clue?

From: Davvid [mailto:notifications@github.com]
Sent: Thursday, August 6, 2015 10:57 AM
To: Azure/msphpsql msphpsql@noreply.github.com
Cc: Luiz Fernando Santos lfsantos@microsoft.com
Subject: Re: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

Updated driver to fix compatiblity with latest head:

https://www.dropbox.com/s/j98z4fd8jh7wr0q/drivers2.rar?dl=0

Verified that the issue is still reproducible under the same conditions.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-128458978.

Hey Davvid,

I used the very first connector you sent me (used both versions in total) and the error below happens:

[13-Aug-2015 20:36:28 America/Los_Angeles] PHP Fatal error: Declaration of DrupalDriverDatabasesqlsrvSchema::addIndex() must be compatible with DrupalCoreDatabaseSchema::addIndex($table, $name, $fields, array $spec) in C:inetpubwwwrootdrupaldriverslibDrupalDriverDatabasesqlsrvSchema.php on line 41

From: Luiz Santos <lfsantos@microsoft.commailto:lfsantos@microsoft.com>
Date: Tuesday, August 11, 2015 at 10:09 PM
To: Azure/msphpsql <reply@reply.github.commailto:reply@reply.github.com>, Azure/msphpsql <msphpsql@noreply.github.commailto:msphpsql@noreply.github.com>
Subject: RE: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

When I’m trying to create the SQL Server database in Drupal 8, I’m getting the following error in the PHP56 error_log file:

[11-Aug-2015 22:04:27 America/Los_Angeles] PHP Fatal error: Call to undefined function DrupalDriverDatabasesqlsrvwincache_ucache_get() in C:inetpubwwwrootdrupaldriverslibDrupalDriverDatabasesqlsrvConnection.php on line 607

Any clue?

From: Davvid [mailto:notifications@github.com]
Sent: Thursday, August 6, 2015 10:57 AM
To: Azure/msphpsql <msphpsql@noreply.github.commailto:msphpsql@noreply.github.com>
Cc: Luiz Fernando Santos <lfsantos@microsoft.commailto:lfsantos@microsoft.com>
Subject: Re: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

Updated driver to fix compatiblity with latest head:

https://www.dropbox.com/s/j98z4fd8jh7wr0q/drivers2.rar?dl=0

Verified that the issue is still reproducible under the same conditions.

Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-128458978.

I verified that this is still reproducible on lateset dev of driver and core.

It just do not run

That is weird, at least you should be seeing an error of some sort. I’ve sometimes experienced the progress bar getting stuck forever, but those bugs were already fixed.

That was exactly the behavior I’ve got.

I’ll continue investigating on my end.

Thanks

From: Davvid [mailto:notifications@github.com]
Sent: Wednesday, September 2, 2015 7:06 PM
To: Azure/msphpsql msphpsql@noreply.github.com
Cc: Luiz Fernando Santos lfsantos@microsoft.com
Subject: Re: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

I verified that this is still reproducible on lateset dev of driver and core.

It just do not run

That is weird, at least you should be seeing an error of some sort. I’ve sometimes experienced the progress bar getting stuck forever, but those bugs were already fixed.

—
Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fAzure%2fmsphpsql%2fissues%2f49%23issuecomment-137301281&data=01%7c01%7clfsantos%40microsoft.com%7cebe800f891614c31d06508d2b4044817%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=uvwgyq5Qcho6vWQNwUmYo7BIzX6YT5onop7xVhDlFrY%3d.

I just posted a repro script for another issue in #50.

I have the feeling that both #49 and #50 might be the same thing as they both seem to exhibit themselves when a PDO exception is thrown (and managed by the user!) while inside a transaction.

So it might be worth taking a look at #50 first given that it is an «easy» stand alone single file repro script.

I am also getting the [Microsoft][ODBC Driver Manager] Function sequence error.

$q = "SELECT * FROM ".TBL_USERS." WHERE username = '$username'"; $stmt = sqlsrv_query($this->connection, $q, array(),array( "Scrollable" => 'static' )); if(!$stmt || (sqlsrv_num_rows($stmt) < 1)){ error_log("getUserInfo failed for $username: $q",3,'error.log'); sqlsrv_free_stmt($stmt); return NULL; } else { /* Return result array */ sqlsrv_next_result($stmt); $dbrow = sqlsrv_fetch_array($stmt, SQLSRV_FETCH_ASSOC); if($dbrow === false) { error_log("dbrow is falsen",3,"error.log"); if( ($errors = sqlsrv_errors() ) != null) { foreach( $errors[0] as $key=>$error ) { error_log("$key -> $errorn",3,"error.log"); } } } elseif (is_null($dbrow)){ error_log("dbrow is NULLn",3,"error.log"); } else { error_log("dbrow is OKn",3,"error.log"); } }
It appears whenever I call the sqlsrv_fetch_array function.

@agrarian What version of driver are you using?

Hi @agrarian, I’m trying to understand your script. Why did you call sqlsrv_next_result() before sqlsrv_fetch_array()? Did you want to test for errors? If you drop sqlsrv_next_result() then there shouldn’t be any problem.

Hi @david-garcia-garcia do you still have function sequence error problem? I looked at the other related issue #50 and your repro script is gone.

I am getting this error:

[unixODBC][Driver Manager]Function sequence error

On both the 4.3.0 release of sqlsrv and 5.1.0 preview. I am running a different framework that is mostly mentioned here (CodeIgniter rather than Drupal). I am afraid I don’t know where to look for the error. Is it an error in the framework, the driver, or unixOBDC? What is the bottom line as far as fixes or workarounds? Thank you.

Hello @rkevinburton
Function sequence error can be caused by various factors, so more info is required in addition to telling us you get this error. Therefore, please create a new issue by providing repro script(s), the platform and/or version of the SQL Server, etc. The more you provide the closer we can get to help answer your questions.

I will try to put together a repro script. But it happens infrequently so it may take me some time to put together a relaiable repro. In the meantime I am connecting to

Microsoft SQL Server Developer (64-bit)
Microsoft Windows NT 6.1 (7601)
NT x64
11.0.6020.0
English (United States)
8192 MB
2 (processors)

I have tried the PHP sqlsrv driver version 4.3.0 and 5.1.0preview, and I get the error on both versions. Though, the error seems to occur less frequently with 5.1.0preview.

From: Jenny Tam [mailto:notifications@github.com]
Sent: Tuesday, October 10, 2017 10:26 AM
To: Microsoft/msphpsql <msphpsql@noreply.github.com>
Cc: Kevin (Ronald) Burton <rburton@agsource.com>; Mention <mention@noreply.github.com>
Subject: Re: [Microsoft/msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

Hello @rkevinburton<https://github.com/rkevinburton>
Function sequence error can be caused by various factors, so more info is required in addition to telling us you get this error. Therefore, please create a new issue by providing repro script(s), the platform and/or version of the SQL Server, etc. The more you provide the closer we can get to help answer your questions.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#49 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AdmtTVpIWEm_hVPqAzkdDEAoYykj5Gilks5sq4yegaJpZM4EPo38>.

Hello @rkevinburton regrettably it’s still a bit vague and we won’t be able to reproduce the problem without a concrete repro scenario. For example, when you encountered this error were you doing a simple select, or update, or insert, with or without using stored procedure, transactions, etc.?

I mostly get errors that look like this:

<body>
<div id=»content»>
<h1>A Database Error Occurred</h1>
<p>Error Number: HY010</p><p>[unixODBC][Driver Manager]Function sequence error</p><p>DELETE FROM users.dbo.users_groups WHERE group_id = 1 AND user_id = 685</p><p>Filename: models/ion_auth_parent_model.php</p><p>Line Number: 1222</p> </div>
</body>

I am using CodeIgniter so admittedly the database code is buried in the MVC handling and is specific to our application.

From: Jenny Tam [mailto:notifications@github.com]
Sent: Tuesday, October 10, 2017 12:07 PM
To: Microsoft/msphpsql <msphpsql@noreply.github.com>
Cc: Kevin (Ronald) Burton <rburton@agsource.com>; Mention <mention@noreply.github.com>
Subject: Re: [Microsoft/msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

Hello @rkevinburton<https://github.com/rkevinburton> regrettably it’s still a bit vague and we won’t be able to reproduce the problem without a concrete repro scenario. For example, when you encountered this error were you doing a simple select, or update, or insert, with or without using stored procedure, transactions, etc.?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#49 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AdmtTYDLshjJzuGIHoxCnSN9amX9KhzXks5sq6Q4gaJpZM4EPo38>.

Thanks @rkevinburton. The problem likely lies in the file models/ion_auth_parent_model.php, line 1222, as indicated in the error message. Looks like something went wrong when trying to delete a certain user? I’m guessing that the user with id 685 and group 1 doesn’t exist.

Please bring this problem to your application developers. FYI, function sequence error often occurs when ODBC functions are called out of the order required. You can check this page for different scenarios that caused HY010 error

If a record doesn’t exist then I get an error that the record doesn’t exist. I am not clear on what ‘function sequence error’ is?

This is the code that is an line 1222

$this->db->delete($this->tables[‘users_groups’], array($this->join[‘groups’] => (int)$group_id, $this->join[‘users’] => (int)$user_id));

From: Jenny Tam [mailto:notifications@github.com]
Sent: Tuesday, October 10, 2017 3:17 PM
To: Microsoft/msphpsql <msphpsql@noreply.github.com>
Cc: Kevin (Ronald) Burton <rburton@agsource.com>; Mention <mention@noreply.github.com>
Subject: Re: [Microsoft/msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)

Thanks @rkevinburton<https://github.com/rkevinburton>. The problem likely lies in the file models/ion_auth_parent_model.php, line 1222, as indicated in the error message. Looks like something went wrong when trying to delete a certain user? I’m guessing that the user with id 685 and group 1 doesn’t exist.

Please bring this problem to your application developers. FYI, function sequence error often occurs when ODBC functions are called out of the order required. You can check this page <https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlfetch-function> for different scenarios that caused HY010 error

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#49 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AdmtTX9i40NUU3qG6TMqFZ50ApxZOcf3ks5sq9DTgaJpZM4EPo38>.

@rkevinburton we cannot investigate further unless we have clear steps to reproduce the problems. I’d happily help when you can provide a repro. In your example above, the error is clearly specific to your application and how the class(es) work(s) underneath.

Closing due to inactivity. Please reopen if necessary.