Can’t save tests in one project – failed to post test
Question ID: 108040

We have one project where we can’t save a new test. We get the error message "Failed to Post Test" after filling in all required fields and clicking OK. This happens even for me when I am logged in as admin. Project passes a Verify Project in site admin with no errors.

Marked as spam
Posted by (Questions: 99, Answers: 7)
Asked on December 19, 2017 6:20 pm
Answers (1)
Private answer

Since it is for more than one user, check a few more to see if it is for ''all'' users.

If it is only for a few users (instead of all) , consider going into Site Admin and delete the ''trouble'' user account and recreate it, and then reassign it to all the projects you/they previously accessed (with appropriate group associations permissions). -- sometimes a user will get ''corrupted'' somehow in the database.

If it is for many or ''all'' users:

Confirm that it is happening for only one (or a few) databases vs. ALL databases/schemas.
All project schemas/databases, might point to the database server/instance or network connectivity having issues.

Look to see if the DRIVE containing the project repository has ample free space. If on Linux, look to see if the ''quota'' is close to macing out. -- Sometimes, when the repository drive is out of space, QC fails with odd errors because it cannot store any more artifacts relating to the project.

In the Database server, have the DBA look to see if the actual database files (under the database, e.g. in MS-SQL all databases have an LDB and MDB file stored somewhere) are being stored on a DRIVE (or in Oracle ''tablespace'') with ample space. -- Sometimes when the database drive is running out of room, QC will throw odd creation errors since new records can't be stored.

Also, ask the DBA is there is any maintenance happening related to this project's schema/database. this will take one or more database/schemas ''offline'' seemingly sporadically.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on December 19, 2017 6:27 pm
Thanks for the troubleshooting tips. I am sorry...this turned out to be a SQL server issue that I didn't realize was happening. Our DBA was restoring a project and something happened and the box ran out of memory. He had to fix the issue and that fixed this issue
( at December 19, 2017 6:29 pm)

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top