ADMS 2024.2 API Calls

[steveh3]

Hello Gang,

Need some help on API calls and how to determine how to point to s a specific SQL server if they have the same name on two different SQL servers.

Here's the case....

We have spun up two new servers (one for ADMS and one for SQL) for testing and are identical to the production server. Only difference is the the old server had ADMS and SQL on same virtual machine.

The new SQL server has the instance name as the old (current production  server) "AutodeskVault".

Installed ADMS 2024.2 on the new server and restored a backup to the new servers and all appears to be working as expected from the Thick Client.

We are now doing some testing with some API calls.

Since we updated the dll’s on the new server to 2024. We are finding out that all of our calls point to  the new server db. Even the old machine lookups are now going to the new db instance. They should still be pointing to the old db on the old server.

We did NOT update the dll’s on the old (current production) servers, only the new SQL server.

Is there a .dll that determines what server to look at so that we pull from the correct SQL db from the correct server?

We have been doing these lookups for about 8 years with probably 5 upgrades and have not run into this before. They only difference is that we split ADMS and SQL into two servers.

Thoughts?

[steveh3]

Hello Gang,

Need some help on API calls and how to determine how to point to s a specific SQL server if they have the same name on two different SQL servers.

Here's the case....

We have spun up two new servers (one for ADMS and one for SQL) for testing and are identical to the production server. Only difference is the the old server had ADMS and SQL on same virtual machine.

The new SQL server has the instance name as the old (current production  server) "AutodeskVault".

Installed ADMS 2024.2 on the new server and restored a backup to the new servers and all appears to be working as expected from the Thick Client.

We are now doing some testing with some API calls.

Since we updated the dll’s on the new server to 2024. We are finding out that all of our calls point to  the new server db. Even the old machine lookups are now going to the new db instance. They should still be pointing to the old db on the old server.

We did NOT update the dll’s on the old (current production) servers, only the new SQL server.

Is there a .dll that determines what server to look at so that we pull from the correct SQL db from the correct server?

We have been doing these lookups for about 8 years with probably 5 upgrades and have not run into this before. They only difference is that we split ADMS and SQL into two servers.

Thoughts?

[manaiah_patil · Accepted solution]

Thank you for sharing the inputs!

As we noticed that you are using the names, could you please try with IP address, especially when we are working with the API calls. The Windows hosts setting file also might help to enforce the correct routing.

[manaiah_patil · Accepted solution]

Thank you for sharing the inputs!

As we noticed that you are using the names, could you please try with IP address, especially when we are working with the API calls. The Windows hosts setting file also might help to enforce the correct routing.

[steveh3]

Thank you Manaiah....

Pretty sure that might be it. We made the change on Friday all appears to be working as expected now.

Thank you,

Steve H.

[steveh3]

Thank you Manaiah....

Pretty sure that might be it. We made the change on Friday all appears to be working as expected now.

Thank you,

Steve H.