Question

"Het argument name mag niet null zijn"

  • 29 March 2024
  • 6 replies
  • 39 views

Userlevel 2
Badge +4

Yesterday I updated the Windows GUI from GUI_2023.3.12.0 to GUI_2024.1.12.0
Today a user complained that his process flow is no longer sending out an email and issues this error:

Any ideas?
In the meanwhile I'll try to see if it is reproducable in an earlier version of the GUI.


6 replies

Userlevel 7
Badge +23

If I would have to guess, the name parameter is not given a value

Userlevel 2
Badge +4

If I would have to guess, the name parameter is not given a value

weird thing is that nothing changed except the GUI.
Could it be that the older GUI version didn't mind?

Userlevel 7
Badge +23

I'm not sure what the process flow does. You do mention emailing, could it be that you are using the SMTP connector but the name parameter was not supplied a value?

I would have to see the stack trace to have a good guess of what is happening, can you reproduce this with executionmode = developer in the INI?

Userlevel 2
Badge +4

ohhh ik zie wel dat ik op mijn systeem wel meer info te zien krijg dan op de pc van de gebruiker.
Ik ga even puzzelen..

Userlevel 2
Badge +4

voor de volledigheid is dit de complete error die ik te zien krijg.
Zo te zien is het niet persé het mailen maar het genereren van het CR report dat als bijlage aan de mail toegevoegd word.
 

Het argument name mag niet null zijn.
Parameternaam: name

Stack trace:
   bij System.Data.DataColumnCollection.get_Item(String name)
   bij System.Data.DataRow.GetDataColumn(String columnName)
   bij Thinkwise.Shared.EditableDataRow.set_Item(String columnName, Object value)
   bij Thinkwise.TSFComponents.TaskReport.FileExportToken.CopyOutputToParameterRow(EditableDataRow parameterRow)
   bij Thinkwise.TSFComponents.TaskReport.ReportExportInvocation.EndInvoke()
   bij Thinkwise.TSFComponents.TSFReporter.BeginExport(FileInfo fi, DataRow parameterRow, IApplicationLogicConnection connection, TSFReport report, TSFController contextController)

Userlevel 7
Badge +23

Indeed Alban, let's keep it English on here for fellow Community members. 

It looks like some development has been done on this front. Can you check the Report parameter that is assigned to the Report property Export path? That might cause this problem to occur when empty.

If that is also not it, please create a ticket for this. 

Reply