Auth failing with SR5

[DannyC]

Had a couple of reports of this already so I tested Swagger UI after upgrading 7.2.1 to SR5.

Doing an Auth via swagger comes up with an error
Method not found: 'Void JiwaFinancials.Jiwa.JiwaApplication.manager.LogEvent'

Pretty keen to get this working again asap without downgrading back to SR4. The 2 clients I've upgraded have both encountered this error so 100% failure rate so far for SR5.

[Scott.Pearce]

IIS or self hosted?

[DannyC]

Self hosted

[Scott.Pearce]

OK, here's what I just did:

Fresh Windows 10 Latest (Azure VM)
Install Jiwa 7.2.1.0
Reboot
Install SQL Server Express 2019
Install SQL Management Tools
Reboot
Install Jiwa 7.2.1.0 SR4
Reboot
Create JiwaDemo on SQL Express (using SQL Management Studio->Import Data Tier Application) and add refreshed licences
Enable, Configure and start Jiwa 7 API Service
Browse to localhost using Microsoft Edge
Click through to SwaggerUI
Logon - OK
Logout
Install Jiwa 7.2.1.0 SR5 (prompted to auto close and attempt to restart Jiwa 7 API - clicked OK).
Reboot
Enable and start Jiwa 7 API Service
Browse to localhost using Microsoft Edge
Click through to SwaggerUI
Logon - FAILED. Same error as you - "Method not found: 'Void JiwaFinancials.Jiwa.JiwaApplication.manager.LogEvent'"

Standby.

[Mike.Sheen]

Works fine for me without installing SR4 before SR5.

[Scott.Pearce]

Workaround:

Stop the API service
Delete the contents of "C:\ProgramData\Jiwa Financials\Jiwa 7"
Start the API service

Problem should no longer exist.

We will continue investigating the cause. Thank-you for your assistance regarding this matter.

[Mike.Sheen]

To reproduce the issue:

1. Install Jiwa 7.2.1 and either no SR or any SR prior to SR4
2. Start the API Service, perform an /auth - all ok
3. Stop the service
4. Install SR5
5. Start the service - perform an /auth and the error occurs.

The cause of the issue is the plugin assemblies were compiled referring to a method signature in JiwaApplication.Manager.LogEvent which changed in SR4. The plugin assemblies need to be recompiled to know about the new signature - and deleting the ProgramData\Jiwa Financials\Jiwa 7 folder forces a recompile of all the plugins.

[DannyC]

any SR prior to SR4...the plugin assemblies were compiled referring to a method signature in JiwaApplication.Manager.LogEvent which changed in SR4

Both clients I installed SR5 were already on SR4. I might be reading this wrong (likely) but that doesn't match with what you say.

Anyway, I'll delete ProgramData\Jiwa Financials\Jiwa 7 and see what happens.

Thanks for the prompt response.

[Mike.Sheen]

Both clients I installed SR5 were already on SR4. I might be reading this wrong (likely) but that doesn't match with what you say.

I've double-checked and the change was made as part of DEV-8730 which was marked as fixed in 7.2.1 SR4 and the date of the code change in our Azure Devops is 25 May 2021 - which was before SR4 shipped - so everything indicates that it was part of SR4... unless we made a mistake and the modified JiwaApplication.dll wasn't included in the patch for SR4 - but we certainly have included it in SR5.

[DannyC]

I've double-checked

Doesn't matter, as long as there's a workaround.

Have just tested on both of those clients...all good! Bit late for them to test so we'll see if there's any yelling tomorrow