[QUOTE=GP2;468138]The manual results page is still giving that error code 11, though.[/QUOTE]

If you email your results, I'll start debugging the problem.

[QUOTE=Prime95;468140]If you email your results, I'll start debugging the problem.[/QUOTE]

OK, I sent files to your alum address. Note the zip files were created on Linux, so the lines are LF-terminated rather than CR LF.

[QUOTE=Prime95;468122]My apologies. I tested this stuff on the test server using prime95 version 29.4 which returns more information (PRP_base and number_of_known_factors).[/QUOTE]

The results file always echos back the full list of known factors, so the parser should be able to infer how many there are. Sometimes they are listed on the same line, sometimes they are listed on a second line:

Mnnnnnnn/fffffffff/fffffff/fffff is not prime

Mnnnnnnn/known_factors is not prime
Known factors used for PRP test were: fffffffff,fffffff,fffff

How does the PRP base work? I always figured it uses a default and only does multiple bases when it thinks it's found a probable prime.

PRP base is always 3 in your prime95 version.

I retested manually reporting (to Primenet) three PRP results, and it now produces:

processing: PRP=(false) for M6600071/3468205309081/52800569
Notice: Undefined index: residue_type in C:\inetpub\www\manual_result\manual_result.inc.php on line 377 Warning: odbc_do(): SQL error: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'AND'., SQL state 37000 in SQLExecDirect in C:\inetpub\v5\v5server\0.95_database.inc.php on line 145 Warning: odbc_do(): SQL error: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'AND'., SQL state 37000 in SQLExecDirect in C:\inetpub\v5\v5server\0.95_database.inc.php on line 145 Warning: odbc_do(): SQL error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert the value NULL into column 'PRP_result64_type', table 'primenet.dbo.t_gimps_cofactor_PRP_results'; column does not allow nulls. INSERT fails., SQL state 23000 in SQLExecDirect in C:\inetpub\v5\v5server\0.95_database.inc.php on line 286
Error code: 13, error text: Insert t_gimps_cofactor_PRP_results failed for M6600071

and similarly for
processing: PRP=(false) for M6600101/1202020373472713

and
processing: PRP=(false) for M6600107/52800857/646810487

Yet, these do show up in my Work Result Details ( [url]https://mersenne.org/results[/url] )

I hope the database is not in some inconsistent state.

What is the way forward? Should we just wait for 29.4 ? I'm not worried about lost time, since it's always possible to fire up extra cloud instances later and get caught up.

I made some changes to the PRP database yesterday, adding a column that identifies the residue type (gpuOwl and prime95 compute different residues).

This of course broke the manual forms. James will fix it soon enough. When he does just resubmit the results.

Automated PRP testing using prime95 29.3 and earlier only partially works. All results should be resubmitted using the manual forms.

[QUOTE=GP2;468410]Notice: Undefined index: residue_type in manual_result.inc.php on line 377[/QUOTE]Manual results form has been fixed, please try resubmitting.

[QUOTE=James Heinrich;468430]Manual results form has been fixed, please try resubmitting.[/QUOTE]

I'll try the form again with a new set of exponents, however for the three specific exponents in question, they can't be resubmitted:

processing: PRP=(false) for M6600071/3468205309081/52800569
Error code: 40, error text: Another computer has already reported this PRP result for M6600071
processing: PRP=(false) for M6600101/1202020373472713
Error code: 40, error text: Another computer has already reported this PRP result for M6600101
processing: PRP=(false) for M6600107/52800857/646810487
Error code: 40, error text: Another computer has already reported this PRP result for M6600107

So please check the database for these three to make sure the null fields in the previous error messages are fixed up.

[QUOTE=GP2;468435]
processing: PRP=(false) for M6600071/3468205309081/52800569
Error code: 40, error text: Another computer has already reported this PRP result for M6600071
processing: PRP=(false) for M6600101/1202020373472713
Error code: 40, error text: Another computer has already reported this PRP result for M6600101
processing: PRP=(false) for M6600107/52800857/646810487
Error code: 40, error text: Another computer has already reported this PRP result for M6600107.[/QUOTE]

These 3 were properly added to the database

I got the same error codes for the next set of exponents, although these were never reported before:

processing: PRP=(false) for M6600119/1320023801/1791760916609809
Error code: 40, error text: Another computer has already reported this PRP result for M6600119
processing: PRP=(false) for M6600133/243940915681
Error code: 40, error text: Another computer has already reported this PRP result for M6600133
processing: PRP=(false) for M6600157/7993318139561
Error code: 40, error text: Another computer has already reported this PRP result for M6600157

Those are in the database -- reported by you.

Are you having mprime report these results to the server? If so, PRP tests with few factors are getting properly recorded (the ones that have the result split across 2 lines are not recorded properly).