I’ve replied to your forum post also on this with the following text – I’m in the same position as you, and unfortunately this won’t be fixed properly until around a month after the next release:
From the error message you receive, it looks like you are using MSSQL - I personally run MSSQL with Mantis in production at work, and have been a developer on mantis for the last 10 years. It is a known issue that support for non-MySQL is problematic in the current release - we are planning to fix this properly by replacing the current database layer shortly after the 1.3 release ( I've been told previously by others in the team we can aim to do with within a month of the 1.3 release), so for now, you may be better off using MySQL or manually patching the issue.
I've been using the following text on the bug tracker for issues relating to other databases:
MantisBT currently supports Mysql and has support for other database engines.
The support for other databases is known to be problematic.
Having implemented the current database layer into Mantis 10 years ago, I'm currently working on replacing the current layer.
If you are interested in using Mantis with non-mysql databases - for example, Oracle, PGSQL or MSSQL, and would be willing to help out testing the new database layer, please drop me an email at firstname.lastname@example.org
In the meantime, I'd advise running Mantis with Mysql Only to avoid issues.
From: Shawn Dibble [mailto:email@example.com]
Sent: 13 June 2014 15:06
Subject: [Mantisbt-soap-dev] mc_issue_add returns error instead of bug id when supplying reporter.
I am using mc_issue_add to submit data to mantis. It works fine and returns the bug id. However if I supply it with a reporter ID, it still creates the issue correctly in mantis, but fails to return the bug id.
I have placed my code in the URL below and was referenced to seek assistance on this mailing list. If anyone could tell me what is going on, that would be great.