search cancel

SpectroSERVER on Windows crashed in libmdlsvutil with Access Violation


Article ID: 208147


Updated On:


CA Spectrum DX NetOps


SpectroSERVER running on Windows crashed with the following details:

ExceptionAddress: 00007ffb6009b484 (libmdlsvutil+0x000000000000b484)
   ExceptionCode: c0000005 (Access violation)

0000009b`358cf450 0000009a`ffd3cb40 : 00007ffb`69188558 0000009c`00af5280 00000000`00000001 ffffffff`fffffffe : libmdlsvutil+0xb484
0000009b`358cf458 00007ffb`69188558 : 0000009c`00af5280 00000000`00000001 ffffffff`fffffffe 00007ffb`5ea39c67 : 0x0000009a`ffd3cb40
0000009b`358cf460 0000009c`00af5280 : 00000000`00000001 ffffffff`fffffffe 00007ffb`5ea39c67 0000009c`583f9f30 : libPort+0x8558
0000009b`358cf468 00000000`00000001 : ffffffff`fffffffe 00007ffb`5ea39c67 0000009c`583f9f30 00007ffb`6009b3df : 0x0000009c`00af5280
0000009b`358cf470 ffffffff`fffffffe : 00007ffb`5ea39c67 0000009c`583f9f30 00007ffb`6009b3df 0000009a`ffd3cb40 : 0x1
0000009b`358cf478 00007ffb`5ea39c67 : 0000009c`583f9f30 00007ffb`6009b3df 0000009a`ffd3cb40 00000000`00000000 : 0xffffffff`fffffffe
0000009b`358cf480 0000009c`583f9f30 : 00007ffb`6009b3df 0000009a`ffd3cb40 00000000`00000000 0000009b`d8446968 : libsskrnl+0xb9c67
0000009b`358cf488 00007ffb`6009b3df : 0000009a`ffd3cb40 00000000`00000000 0000009b`d8446968 0000009a`a27717c0 : 0x0000009c`583f9f30
0000009b`358cf490 0000009a`ffd3cb40 : 00000000`00000000 0000009b`d8446968 0000009a`a27717c0 0000009a`9c8eb260 : libmdlsvutil+0xb3df
0000009b`358cf498 00000000`00000000 : 0000009b`d8446968 0000009a`a27717c0 0000009a`9c8eb260 00007ffb`6009708d : 0x0000009a`ffd3cb40


The crash was caused by a corrupted model. The SpectroServer crashed while creating sub-interfaces for this model.

The model handle can be determined from the .dmp generated file in the $SPECROOT\SS\Support directory. Collect the dump and open a Support case and attach the dump file.
The Engineering team will be able to identify the offending model.


DX NetOPS Spectrum 20.2.5



The crash is caused by a corrupted model. Once the model handle has been identified, determine it's type.

If the above model is a device model, then you can delete and re-discover the device.

If the above model is an application model, then you will need to initialize to a legacy DB and then load the models only (-m) load from a previously saved good DB backup.
Initialize to a Legacy DB
Load a Database