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: Update Service not finding messages
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
‎Mar 25, 2003
03:28 PM
Update Service not finding messages
From one computer, the Update Service is informing me that I have no messages, when in fact there are messages. I get the same results via "agent.exe -au ..." as well as programatically through the object model. But if I do "agent.exe -dm ...", I find that there are in fact messages.
Only one computer is acting this way. Others are finding the messages with no problems.
What should I be looking for?
Only one computer is acting this way. Others are finding the messages with no problems.
What should I be looking for?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2003
03:42 PM
Just to confirm.... you are saying that the running the following two commandline options give different results on one machine...
1. Agent -au{your product coce} -AppMenu
2. Agent -dm{your product coce}
.....check the version of your product installed on that one machine. To do that, open the Test Utility provided in the ISUS SDK on the problem machine. Expand your product. Look at the version field. Compare this to a machine that is working properly. This will confirm that the ISUS believes these are the same product/version.
Let me know what you find with the versions.
1. Agent -au{your product coce} -AppMenu
2. Agent -dm{your product coce}
.....check the version of your product installed on that one machine. To do that, open the Test Utility provided in the ISUS SDK on the problem machine. Expand your product. Look at the version field. Compare this to a machine that is working properly. This will confirm that the ISUS believes these are the same product/version.
Let me know what you find with the versions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2003
03:43 PM
Also, what is the message when you run from the 'bad' machine? Do you see the "no updates available" message?