1 reply to this topic

[joziMcK]

 Hello,

 

When I tried to the export the results of my most recent NCA, I got the message below that I'm not quite sure how to interpret, and the export failed. Clearly, something in my project is too long, but what? I thought it might be that my worksheet was too long and generated too long of an output, but I just ran the NCA on a new worksheet containing only half of the original data and got the same message. Any ideas on how to fix this?

Thanks. 

 

 

Message:
 Phoenix has encountered an unexpected error.
You can continue but it is suggested that you do not save over your
 originally loaded projects to prevent data loss.
Details:
 Specified argument was out of the range of valid values.
Parameter name: Text length cannot be more than 32767

Stack Trace:
   at Syncfusion.XlsIO.Implementation.SSTDictionary.CheckLength(Object key)
   at Syncfusion.XlsIO.Implementation.SSTDictionary.AddIncrease(Object key, Boolean bIncrease)
   at Syncfusion.XlsIO.Implementation.RangeRichTextString.EndUpdate()
   at Syncfusion.XlsIO.Implementation.RangeImpl.set_Text(String value)
   at Syncfusion.XlsIO.Implementation.RangeImpl.OnValueChanged(String old, String value)
   at Syncfusion.XlsIO.Implementation.RangeImpl.set_Value(String value)
   at Syncfusion.XlsIO.Implementation.RangeImpl.SetSingleCellValue2(Object value)
   at Pharsight.Phoenix.Services.Grids.FileHandlers.ExcelFileHelper.CopyWorksheetToExcelSheet(ExcelFileSaveProperties properties, IWorksheet worksheet, IWorksheet excelWorksheet, Int32 startRowIndex) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Grids\FileHandlers\ExcelFileHelper.cs:line 116
   at Pharsight.Phoenix.Services.Grids.FileHandlers.ExcelFileHelper.CopyWorksheetToExcelSheet(ExcelFileSaveProperties properties, IWorksheet worksheet, IWorksheet excelWorksheet, IWorksheet historyWorksheet) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Grids\FileHandlers\ExcelFileHelper.cs:line 33
   at Pharsight.Phoenix.Services.Grids.FileHandlers.ExecutableResultsWorkbookFileHandler.ExportToStream(Stream outputStream, Guid categoryId, Object obj, Object data) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Grids\FileHandlers\ExecutableResultsWorkbookFileHandler.cs:line 141
   at Pharsight.Phoenix.Services.Eventing.FileSystem.SaveObjectToFile(Object objToSave, String fileName, Object exportData, Boolean overwriteExisting) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Eventing\FileSystem.cs:line 1132
   at Pharsight.Phoenix.Services.Eventing.FileSystem.PerformAdvancedExportForFile(Object objToSave, String fileName, Boolean clearHistory) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Eventing\FileSystem.cs:line 2061
   at Pharsight.Phoenix.Services.Eventing.FileSystem.SaveObjectToFile(Object objToSave, Boolean objIsWorkflow) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Services.Eventing\FileSystem.cs:line 891
   at Pharsight.WinNonlin.Plugins.SystemViewers.ImportExport.FileCommandsContainer.WaitCursorForAction(Action action) in c:\jenkins\workspace\PhoenixCompile\PHX\MAIN\Phoenix\App\Plugins.SystemViewers\ImportExport\FileCommandsContainer.cs:line 249
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

[Simon Davis]

Hi Jozi, by the looks of the message I think you are exporting to Excel, can you try exporting go CSV instead?

 

Otherwise I have not seen this message before so I'd like to see a copy of a project that exhibits this behaviour and clarificaiton on exactly what steps/output you are attempting to export that triggers this message so we can try and replicate to assess how to fix.

 

Please let us know how you get on and if you send the case to Support please let me know the case number assigned, thanks.

 

 Simon.