View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0024302||mantisbt||db mssql||public||2018-04-17 13:25||2018-04-29 19:21|
|Reporter||Jose Lozano||Assigned To||community|
|Priority||high||Severity||major||Reproducibility||unable to reproduce|
|Status||closed||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0024302: The consecutive ID of incident record number is skipped, sometimes one 3 times and sometimes 4 consecutive. it does not throw er|
I need your help, since it is happening to me that when several users are working on Mantis, from one moment to another the consecutive ID number of incidence record is skipped, sometimes one sometimes 3 and sometimes 4 numbers, losing the control and follow up. I would like to know if someone has happened to him, why it happens and how it can be solved.
I appreciate the help.
|Tags||No tags attached.|
I am not complete sure if I understand your problem.
If so and if you are using MySQL, check database auto_increment settings.
Hello, thank you for your quick response. but the problem is that he is numbering well, with the consecutive one at a time, but from one moment to the next he increases the numbering, for example he jumps from 192 to 196 and the numbers 193-194-195 are lost and when looking for them He says they do not meet. If I use MYSQLExpress. I appreciate your guidance.
Isn't this what I wrote before?
What's the output of
If all displayed values are 1, you have to provide the additional information listed below
• Exact version of PHP, 7.1.7 Database, IIS Web server, Browser Chrome and Operating System Windows Server 2012
Still missing a clear information about your database.
Sorry I can't help as I don't use this database.
I recommend to use MySQL or MariaDB as most of the Mantis developers and users are using it.
I appreciate your collaboration, guidance and the time you have dedicated me. have a happy day.
This not a MantisBT issue. The sequence numbers are assigned by the RDBMS. I believe you're most likely facing a known issue with SQL server, see
I'm sorry, but there is absolutely nothing that we can do about it.
Also, please note that having non-sequential issue IDs is technically not a problem - The ID is just that - a unique identifier; you would also have gaps e.g. if you have multiple projects (issues are unique across the whole instance) or if you delete issues.
@dregad all you said about non-sequential Ids is right, but the stackoverflow link
Jose could you please provide additional info about:
Dregad and obmsch, I appreciate your interest in supporting me and in your effort to try to solve my problem.
attached the requested information:
1.SQLSERVER (EXPRESS) Version: SQL 2012 Express.
Again to the two thanks for all your bearings.
Jose, as said I will try to reproduce what you are seeing in my environment, but
You are talking about already registered issues, I was asking for new submits (issues)
Completed run tests with the following setup:
Setting up the test environment I ran in a couple of problems. I put them here and let
Follow-up in 0024347
Just to be sure, you was that due to the e-mail queue filling up and not being processed ?
@dregad the rest request time out (iis time out). Looked like internal processing doesn't finish. The email table
Setting to resolved as this is not a Mantis but a database issue.
Thanks @obmsch for your support.
|2018-04-17 13:25||Jose Lozano||New Issue|
|2018-04-18 02:24||atrol||Status||new => feedback|
|2018-04-18 02:24||atrol||Note Added: 0059579|
|2018-04-18 08:13||Jose Lozano||Note Added: 0059584|
|2018-04-18 08:13||Jose Lozano||Status||feedback => new|
|2018-04-18 08:37||atrol||Status||new => feedback|
|2018-04-18 08:37||atrol||Note Added: 0059585|
|2018-04-18 09:10||Jose Lozano||Note Added: 0059586|
|2018-04-18 09:10||Jose Lozano||Status||feedback => new|
|2018-04-18 09:11||Jose Lozano||Note Edited: 0059586||View Revisions|
|2018-04-18 09:26||atrol||Status||new => feedback|
|2018-04-18 09:26||atrol||Note Added: 0059587|
|2018-04-18 09:38||Jose Lozano||Note Added: 0059588|
|2018-04-18 09:38||Jose Lozano||Status||feedback => new|
|2018-04-18 09:48||atrol||Category||administration => db mssql|
|2018-04-18 09:51||atrol||Note Added: 0059589|
|2018-04-18 09:54||Jose Lozano||Note Added: 0059590|
|2018-04-18 12:33||dregad||Assigned To||=> dregad|
|2018-04-18 12:33||dregad||Status||new => resolved|
|2018-04-18 12:33||dregad||Resolution||open => no change required|
|2018-04-18 12:33||dregad||Note Added: 0059594|
|2018-04-18 14:18||obmsch||Note Added: 0059595|
|2018-04-18 14:29||atrol||Assigned To||dregad => community|
|2018-04-18 14:29||atrol||Status||resolved => feedback|
|2018-04-18 14:29||atrol||Resolution||no change required => reopened|
|2018-04-18 14:52||Jose Lozano||Note Added: 0059596|
|2018-04-18 14:52||Jose Lozano||Status||feedback => assigned|
|2018-04-18 16:34||obmsch||Note Added: 0059597|
|2018-04-22 05:06||obmsch||Note Added: 0059628|
|2018-04-23 07:17||dregad||Note Added: 0059645|
|2018-04-23 08:21||obmsch||Note Added: 0059646|
|2018-04-29 10:00||atrol||Status||assigned => resolved|
|2018-04-29 10:00||atrol||Resolution||reopened => no change required|
|2018-04-29 10:00||atrol||Note Added: 0059703|
|2018-04-29 19:21||vboctor||Status||resolved => closed|