DIAdem 2012 crashes on commandline execution

[MartinKozlowski]

Hi there,

i'm trying to execute DIAdem 2012 on a Windows 2008 R2 Server via Commandline (for automatic report generation). To check if DIAdem did successfully, i have to start and exit DIAdem for each execution, so i can't use OLE-Communiction. I tried some some things, but it occurs that DIAdem can't handle to long startparameters and crashes.

If i try the same commandline on my Win7 PC DIAdem just won't start.

Here the commandline:

"C:\Program Files (x86)\National Instruments\DIAdem 2012\DIAdem.exe", /CT1:="C:\Users\mdmsrv17\AppData\Local\Temp\2\odssession.ior", /CT2:="C:\Users\mdmsrv17\AppData\Local\Temp\2\entries", /CT3:="C:\Users\mdmsrv17\AppData\Local\Temp\2\diadem6853541499671121548.props", /CT4:="C:\Users\mdmsrv17\AppData\Local\Temp\2\diadem765430454232149179.error", /CT5:="1", /CT6:="repCool", /CT7:="asdf", /CT8:="qadfsfaf", /CT9:="ycvyxv", /CT10:="rtzu", /Cscriptstart("D:\TestServer\MDMHKL_DIAdemConvertServer\vwg.audi.mdm.diadem.launcher_1.6.0.jar\..\.\configuration\diadem\loadReport.VBS")

And here is the crash-report:

Problem signature:

Problem Event Name: APPCRASH
Application Name: DIAdem.exe
Application Version: 12.0.1.5436
Application Timestamp: 52895d1f
Fault Module Name: DIAdem.exe
Fault Module Version: 12.0.1.5436
Fault Module Timestamp: 52895d1f
Exception Code: c0000005
Exception Offset: 00008fee
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1031
Additional Information 1: ac47
Additional Information 2: ac4739eb0284c411d27031b8b9b5d692
Additional Information 3: a543
Additional Information 4: a543e2c1d6b4df0a214f63972958f6da

With best regards,

Martin Kozlowski

[Walter_Rick]

Hi Martin,

We need to check whether there is a limit of the command line parameter string. But as a work-around you can use a start script which contains all settings you need. The start script is part of the DIAdem configuration and runs directly after launch.

Greetings

Walter

[MartinKozlowski]

Hi Walter,

the parameters are dynamically generated, so i can't use a fixed startscript.. The Programm which starts DIAdem just builds a commandline (with the T-Parameters and a startscript) and executes it.

It seems that the limit isn't the number of the parameters, but the length of the complete line.

Greetings

Martin

[Walter_Rick]

Hi Martin,

Yes, it is possible that it is the length, but it takes some time to analyze the problem and some more time to get a solution – if possible in general. So it could help to have a work-around.

It seems to me that your start parameters are a list of single command steps. If you create this dynamically why can you no create a start script dynamically? It looks like this:

T1="C:\Users\mdmsrv17\AppData\Local\Temp\2\odssession.ior"

T2="C:\Users\mdmsrv17\AppData\Local\Temp\2\entries"

T3="C:\Users\mdmsrv17\AppData\Local\Temp\2\diadem6853541499671121548.props"T4="C:\Users\mdmsrv17\AppData\Local\Temp\2\diadem765430454232149179.error"

T5="1"

T6="repCool"

T7="asdf"

T8="qadfsfaf"

T9="ycvyxv"

T10="rtzu"

Call scriptstart("D:\TestServer\MDMHKL_DIAdemConvertServer\vwg.audi.mdm.diadem.launcher_1.6.0.jar\..\.\configuration\diadem\loadReport.VBS")

Greetings

Walter

[MartinKozlowski]

Hi Walter,

thank you, i will share your solution with the developers, but it will take some time.

Greetings,

Martin

[Brad_Turpin]

Hey Martin,

Are you wanting to run more than one DIAdem instance at the same time this way?  If not, you could use a startup VBScript that looks to the same ASCII or XML or TDMS file for the dynamic parameters.  Then you can update the parameter file each time before calling DIAdem.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[MartinKozlowski]

Hi Brad,

actually i got two instances running. One for data conversion (works fine) and one for report generation, for wich i need some parameters. My workaround is to hide as many parameters as i can in the meta-data of the mass-data, but that's an ugly one.

Greetings,

Martin

[MartinKozlowski]

Hi,

i figured out, i've got a properties-file in which i can put the parameters. If i name the parameters other than T1 to T10, the programm won't put it in the command line. So that problem is sovled 🙂

But can you analyze why DIAdem is crashing, if the commandline-string is longer than 500?

Greetings,

Martin

[Brad_Turpin]

Hi Martin,

I believe this is a Windows restriction on the command line length, but I'm not an expert.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[MartinKozlowski]

Hi,

considering this post, windows should at least support a length of 2k signs... click. But maybe that's just theoretical 🙂