Update VAF 23.6.687.5 vault is unstable

Hi,

I have upgrade my VAF Application with VAF 23.6.687.5. (MFilesAPI is in version 23.9.12966.6)

This project use a custom library compiled with MFilesAPI version 23.9.12966.6

The compilation and the VAF application install are correct (no error) but the MFAppPlateform stops and starts continuously.

In the event observer I have :

1-Information : coffre "CAIR_QUALIF" est en ligne. ID du coffre : {6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}

2-Warning : CAIR_QUALIF ({6B31CC31-CFEB-4068-ACC0-FBC8B23315B6})
M-Files Network Folder Connector: Network Folder, P:Fournisseur (fbc66a819a1e48fea62e7864df3a5a4f): Indexing is enabled for this external repository connection but the indexer user has not been authenticated. Either authenticate the indexer user or disable indexing for this connection.

and I have no error when the VAF starts and stops.

I don't want return in version 2.2 and I need to make change for my customer, I don't know where to look

M-Files Server is in version :23.9.12966.6

Best regards

Top Replies

psilhol 3 months ago in reply to psilhol +1 verified

Sorry Craig, I think I found the reason for this instability. I had renamed a previous.mfappx in the compilation directory and I therefore had an mfappx in the mfappx therefore 2 VaultApplication. …

Parents

0 Craig Hawker 3 months ago
I'm not aware of any general issues like that with that release.

A few questions:

Have you tried with the most recent VAF release?

Are you overriding any of the lifecycle events (startapplication, startoperations, etc.)? If so, are you calling the base implementations?

Does this behaviour happen on your machine as well? If so then can you attach a debugger ("System.Diagnostics.Debugger.Launch") and see what's happening?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 psilhol 3 months ago in reply to Craig Hawker

Hi Craig,

I have launch the debugger and I have an exception in MFAppPlateform.exe whithout comment.

The MFAppPlateform stops after the line base.StartOperations(vaultPersistent) and restart automaticaly.

In the event observer I have just a warning when the MFAppPlateform restarts.

Best regards

I don't know to insert a screenshot in this answer, how can I send it to you ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 3 months ago in reply to psilhol

Show me that override and the stack trace.

You should be able to paste an image into this box (take a screenshot, copy it to your copy buffer, then ctrl-v - or the regional equialent - to paste here).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Craig Hawker 3 months ago in reply to psilhol

Show me that override and the stack trace.

You should be able to paste an image into this box (take a screenshot, copy it to your copy buffer, then ctrl-v - or the regional equialent - to paste here).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 psilhol 3 months ago in reply to Craig Hawker

OK but I send it you by email
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 psilhol 3 months ago in reply to psilhol
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 3 months ago in reply to psilhol

No, please put it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 3 months ago in reply to Craig Hawker

Click to attach the debugger. See what the stack trace is in the exception.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 psilhol 3 months ago in reply to psilhol

Hi,

The stack

'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Bin\x64\MFDynamicCLRObjectBridge.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Bin\anycpu\MFiles.Common.Definitions.Identity.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Server\Data\Apps\{6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}\{B8806BB6-0922-4D2D-A82A-16A6C2F77F1D}-ISij3BB3ORJKRljCyUDTpIhepEsCsptWgidvOyxbDpc=\XONYX.dll'. Les symboles ont été chargés.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Server\Data\Apps\{6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}\{B8806BB6-0922-4D2D-A82A-16A6C2F77F1D}-ISij3BB3ORJKRljCyUDTpIhepEsCsptWgidvOyxbDpc=\MFiles.VAF.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\assembly\GAC_MSIL\Interop.MFilesAPI\7.0.0.0__f1b4733f444f7ad0\Interop.MFilesAPI.dll'. Le module a été généré sans symboles.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Server\Data\Apps\{6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}\{B8806BB6-0922-4D2D-A82A-16A6C2F77F1D}-ISij3BB3ORJKRljCyUDTpIhepEsCsptWgidvOyxbDpc=\MFiles.VAF.Configuration.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Server\Data\Apps\{6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}\{B8806BB6-0922-4D2D-A82A-16A6C2F77F1D}-ISij3BB3ORJKRljCyUDTpIhepEsCsptWgidvOyxbDpc=\XOutils.dll'. Les symboles ont été chargés.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Remote Debugger\x64\Runtime\Microsoft.VisualStudio.Debugger.Runtime.Desktop.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_64\CustomMarshalers\v4.0_4.0.0.0__b03f5f7f11d50a3a\CustomMarshalers.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'QMSDynamicAssembly'.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'Microsoft.GeneratedCode'.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\mscorlib.resources\v4.0_4.0.0.0_fr_b77a5c561934e089\mscorlib.resources.dll'. Le module a été généré sans symboles.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Program Files\M-Files\23.9.12966.6\Server\Data\Apps\{6B31CC31-CFEB-4068-ACC0-FBC8B23315B6}\{B8806BB6-0922-4D2D-A82A-16A6C2F77F1D}-ISij3BB3ORJKRljCyUDTpIhepEsCsptWgidvOyxbDpc=\Newtonsoft.Json.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'MFAppPlatform.exe' (CLR v4.0.30319: DefaultDomain) : Chargé 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
Le programme '[21256] MFAppPlatform.exe' s'est arrêté avec le code -1 (0xffffffff).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 psilhol 3 months ago in reply to psilhol

Hi,

I have delete the VAF V23 and install VAF v2.2.0.11 and the vault works very well.

I'm waiting for your return to do the tests gain.

Best regards
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
+1 psilhol 3 months ago in reply to psilhol

Sorry Craig,

I think I found the reason for this instability.
I had renamed a previous.mfappx in the compilation directory and I therefore had an mfappx in the mfappx therefore 2 VaultApplication.

The test vault is stable with the new VAF application in V23

All my apologies and have a nice day
Cancel
Vote Up +1 Vote Down

Sign in to reply

Reject Answer

Cancel
0 Craig Hawker 3 months ago in reply to psilhol

Hi @psihol

I am not sure what's happening here. I don't see anything in the information you've given me that gives me a clear understanding of what's happening. That VAF release has been out for 6 months so it's unlikely there's a fundamental issue. As I said before: perhaps try with the latest release, although I'm not sure what's causing the issue so I can't say whether it might help.

If you need more support than this forum can provide then you may want to reach out to your local partner team.

Regards,

Craig.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 3 months ago in reply to psilhol

Great to hear that it's sorted!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel