I have created this thread to save all the recent error reports.
Two folks have just reported this error when uploading a S2S CSV log file
73 Barry N1EU
The activator file could be uploaded without problems, only the chaser file goes into hick-up.
For me it’s the other way round. Uploaded the chaser log but the activator log got kicked back…
73, Sylvia OE5YYN
Entered my activator and S2S (chaser) contacts manually (i.e. not a CSV file) - all went fine.
I just tried entering my log manually for today’s activation and it failed on the last step after you click “I agree”.
Same problem here.
Error says the server has run out of file space. That’s why the csv are not found (because they can not be uploaded). I guess
Excellent event! But I cannot uploaded the chaser and the activator log.
73 de HB9BIN, Jürg
I cannot manually enter chaser or activator logs…
I’ve been back about 30mins from the GM Microwave Roundtable and have been investigating what was happening. It appeared there was no disk space on the server and my control panel file manager was not responding. I submitted a ticket reporting the error and popped to the loo for about a minute. On my return the file manager is responding and says we have 4GB of file space at least.
It looks like something was broken on the server and it has been fixed. Whether it was a result of my ticket we’ll never know as that would be a fast response. It’s 2315Z now. If you want to try a log upload, wait till gone 2330Z just to let the load drop on the servers as probably other customers who share the service may be hitting the server hard after it has come up. I’ll see if it’s working in the morning or if there are more issues to resolve.
Still not working. 2343z
0139 NOT WORKING
Yes, still getting same error when uploading chaser/s2s csv
It won’t take my manually typed activator log - same message.
The database did accept a large bunch of single, manually-typed chaser logs with no problems. It also accepted a single S2S entry.
It still can’t accept my activator log with 40 entries, although it has saved it OK in the initial form, and it’s still sitting there. I’m wondering if I’ll have to re-type the whole thing before this is over…
04/11/2018 06:52 UTC: No difference if “import” or “submit”.
Still no disk space.
Blockquote An error has occured whilst saving the Activation Details :
System.ApplicationException: Database Error Adding Activator Entry —> System.Data.SqlClient.SqlException: Could not allocate space for object ‘dbo.ActivatorLogs’.‘PK_ActivatorLog’ in database ‘sotadata_db’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action
1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at SOTA.AddActivatorEntry.AddEntry(SqlConnection dbConnection, Int32 userID, String ownCallsign, Int32 summitID, DateTime activationDate, DataTable QSOTable, String& QSODetails) in c:\SOTA\SOTADATABASE_Net45\AddActivatorEntry.cs:line 302 — End of inner exception stack trace — at SOTA.AddActivatorEntry.AddEntry(SqlConnection dbConnection, Int32 userID, String ownCallsign, Int32 summitID, DateTime activationDate, DataTable QSOTable, String& QSODetails) in c:\SOTA\SOTADATABASE_Net45\AddActivatorEntry.cs:line 319 at SOTA.AddActivation3.Button1_Click(Object sender, EventArgs e) in c:\SOTA\SOTADATABASE_Net45\AddActivation3.aspx.cs:line 83
I could just upload my chaser/S2S file, but the activator file had the same problem. Also entering QSO’s manually doesn’t help, error after clicking “I agree”.
Need to go back again I’d say.