You are viewing limited content. For full access, please sign in.

Question

Question

Force Forms to start on higher Instance ID?

asked on August 21, 2019

We're migrating our Forms install to a new server and I noticed that on the new server, the Instance ID for Forms restarts (so that the first form submitted on the new server has an Instance ID of 1).

We use Instance IDs in several workflows to reference documents submitted by Forms, and we'll have to change those workflows to avoid accidental duplicate IDs if the Forms Instance ID is restarted.

Is there a way to force Forms to start at a higher Instance ID on a new install?

0 0

Answer

SELECTED ANSWER
replied on August 21, 2019

By any chance did you use a newer version of Forms on the new sever?

It is possible that installing a newer version and pointing it at an existing database from an older install might miss important parts of the upgrade process.

Also, when you installed the second server, did you disable the old one (or at least the routing service) to make sure there were no conflicts?

1 0

Replies

replied on August 21, 2019

It sounds like you are not just moving Forms to a new server, but setting up a whole new Forms installation. The instance IDs are unique inside the Forms database itself, so just moving the Forms installation should not restart the instance IDs at 1. If you use the same database it should pick up right where you left off.

0 0
replied on August 21, 2019

Thanks Blake,

I guess I'm misunderstanding what "just moving the Forms installation" would entail. When I tried to install Forms on the new server pointing to the old database, the Instance IDs did not restart (as you said), but trying to submit forms resulted in unexpected errors, so I felt that was probably not the best method of migration. Granted, I haven't looked at the errors in detail.

Do you know of any available instructions for Forms migration to a new server using the old database?

0 0
replied on August 21, 2019

I'm not aware of any written instructions for that process. Have you reached out to your Solutions Provider?

0 0
replied on August 21, 2019

Not yet--but that sounds like my next step. Thanks

0 0
SELECTED ANSWER
replied on August 21, 2019

By any chance did you use a newer version of Forms on the new sever?

It is possible that installing a newer version and pointing it at an existing database from an older install might miss important parts of the upgrade process.

Also, when you installed the second server, did you disable the old one (or at least the routing service) to make sure there were no conflicts?

1 0
replied on August 28, 2019

Redoing the process and making sure I had the old Forms Routing Service turned off, it now works. My best guess it that I had forgotten to turn it off the first time.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.