I'm getting an IDispatch error 11517 when I attempt to enumerate updates. I have nooooo idea what that means, since the help specifies error - 11000 = http status code, so 517? Anyone ever see this before? I only have this issue across 2 particular subnets in my company.
What ports does the update service use for notifications, just HTTP (80) right?
I would like to investigate this error. I have a few questions:
1. Are you hosting the Update Service or is InstallShield hosting it? 2. Does this product/version have any updates? 3. If so, are they informational messages or software updates? 4. Are you using Visual Basic or C++ for your enumeration code? 5. What version of Agent.exe do you have (C:\Program Files\Common Files\InstallShield\Update Service)? 6. Does this happen on one particular machine or on all machines? 7. Do the machines in the two subnets go through a proxy or a specific firewall?
1. Are you hosting the Update Service or is InstallShield hosting it? We are.
2. Does this product/version have any updates? Yes, the update works fine between other networks.
3. If so, are they informational messages or software updates? Software updates.
4. Are you using Visual Basic or C++ for your enumeration code? C++
5. What version of Agent.exe do you have (C:\Program Files\Common Files\InstallShield\Update Service)? Latest SDK from the update service website.
6. Does this happen on one particular machine or on all machines? All machines in on the subnet.
7. Do the machines in the two subnets go through a proxy or a specific firewall? I'm fairly sure it goes through a firewall... but I'm not 100% sure of configuration.
It's just our QA network and I beleive we're deciding the tester can simply test from our corp. network. Though, I'm still interested in what that error even means?
Though, I'm still interested in what that error even means?
So are we :).
Few more questions: 1. Does this happen only for your enumeration code? What happens if you call AppUpdate.AppStart or AppUpdate.AppMenu? Does it cause any errors or does the update actually work?
2. What happens if you check for updates from Agent.exe via command line:
Ok, I've got a little more info from our networking ppl... and they think it has something to do w/ the following :
Test servers are in the QA enviornment, they have internal/external addresses, we're using the external. They beleive that the loop-back involved is getting blocked by our firewalls for some reason.
I'll do the test command line agent test and give my results as soon as a i get a chance...
