Revision Table fails to update when Vault 2022.4 server is configured for SSL

[pvillella-CAP]

SSL enabled: Revision Table doesn't properly update (all other Vault features work as expected.)

No-SSL: Everthing works perfectly!

I've been working on this issue with the Autodesk Support team and I want to see if anyone else has run into it.

Configuring Vault 2022.4 for SSL is a breeze! I've got a valid certificate installed and when in SSL mode I can connect from the clients and job processors using https and the FQDN. Everything works 100% as expected. Except...

For some bizarre reason, we've noticed that the Vault revision table in our AutoCAD drawings is NOT updating when the server is in SSL mode. We include the Lifecycle State in our rev table and when we change the State of a drawing, this value should update in our revtable. It does not. I still see the events in the history and it says it updates the Revision Table but nothing happens.

As soon as I set the server back to non-ssl (http) and log the client and job processor in using just the server name, everything works as expected.

Have you seen this before? Any idea why this one specific event is not working properly when configured for SSL?

It's a strange one, right?

Cheers!

Patrick

[peggy_zhuY2FUY]

Could you try to use update properties command in AutoCAD to see if new state is updated? Thanks.

[pvillella-CAP]

Hi @peggy_zhuY2FUY . Yes, the revision table updates perfectly when I use the Update Properties tool in AutoCAD.

It's just when the state is changed in Vault that the update fails.  The log on the job processor shows that it updated the revision table but it never actually updates it.

Again, as soon as I disable SSL and go back to normally http mode, things work as expected.

Thank you,

Patrick

[peggy_zhuY2FUY]

Hi @pvillella-CAP , thank you for trying and letting me know the Update property command can work.

Most likely it's a bug and we can reproduce it at our end. And I can see the problem also happens even in the server without SSL, but it's ok at your side. would you share some screenshot of your configuration and revision table? I want to see what the difference is.

Thank you, Peggy.

[pvillella-CAP · Accepted solution]

Hi @peggy_zhuY2FUY,

Thanks for jumping in. I have good news to report. I've discovered a solution, even while using SSL.

The solution:

On each of your job processor machines, make sure to log into Vault at least once using the new path (in my case, the https FQDN path), using either the Vault client or the Vault add in for AutoCAD. After that, everything works!

Background info:

There is a file named WorkingFolders.xml that establishes your working folder for Vault that must be present on the job processor system, in the directory that corresponds to your server name. If you are using SSL, this directory will begin with https.

For example:

On my job processor machine, this path is:

"C:\Users\USERNAME\AppData\Roaming\Autodesk\VaultCommon\Servers\Services_Security_6_29_2011\[email protected]\Vaults\YOUR_VAULT_NAME\Objects\WorkingFolders.xml"

This WorkingFolders.xml file is only created when you actually log into the Vault on the job processor machine using either the Vault client or via the Vault add in for AutoCAD.

Simply launching the Autodesk Job Processor app creates the folder but does not create the WorkingFolders.xml file.

What I found is that if this .xml file does not exist for the folder of the Vault you are connected to, then the Vault Job Processor does not update the drawing properties or update the revision table as expected.  I believe this is because it ends up downloading to a default folder instead of the folder it should download it to when working folders are enforced.  If you don't enforce working folders on your Vault, maybe you will never run into this issue. 

As long as that file exists, everything works perfectly, whether I have the Vault server set to http or https.

Again, note that if you were using your Vault server in http mode (i.e. not secure) and then switch to https (secure) mode, you will need to log into the Vault from the Vault client (or Vault add in for AutoCAD) on EVERY one of your job processor systems at least once. This will create the .xml file in the directory that corresponds to your https path.

On one of my job processor systems, I had logged in while using http but had not done so yet after switching to https. This is why the revision table was updating correctly when I was using http but would fail to update when I set it to https. Now, it's updating as expected regardless of what mode I have the server set to.

This was a really tricky issue to figure out but the solution ended up being very simple! I like that 🙂

I hope this post helps someone else out.

Patrick

[peggy_zhuY2FUY]

Hello Patrick,

Thank you so much for the details and your solution. It's so glad to hear you found the cause and fixed the issue.

I will try out your solution to see if it can help at my end.

Thanks again.  Peggy