This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: FLEXnet Connect Issues
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 21, 2007
04:45 PM
FLEXnet Connect Issues
Has anyone else been having FLEXnet Connect issues? I have been trying to add a new upgrade and it has been giving me problems. Here are the steps I took:
- Create a new Product called Product 1
- Create a new version of Product 1
- Create a new update, listing Product 1 version as a target
- Set update into test mode
- Use the Test Update feature in FLEXnet
- app starts up, you can see the product code as part of the URL
- Get an error, 13001: Product not registered with Update Service
This seems odd to me since I just entered all that information. Also, it is that information which it is using to launch the test app, so the product information must match!
- Create a new Product called Product 1
- Create a new version of Product 1
- Create a new update, listing Product 1 version as a target
- Set update into test mode
- Use the Test Update feature in FLEXnet
- app starts up, you can see the product code as part of the URL
- Get an error, 13001: Product not registered with Update Service
This seems odd to me since I just entered all that information. Also, it is that information which it is using to launch the test app, so the product information must match!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 17, 2008
07:33 AM
This may be too little too late... But we have found that in the "version" field when registering a product, FLEXnet Connect is not able to read past X.X . So for instance, if your product is 5.1.2 the ".2" is not read and will actually cause the product to appear as "unregistered". (In our case, we have had to use just X.X for the version, and versioning on our DLLs for the logic to actually deliver the update to the user).
I hope this helps.
I hope this helps.