"Could not get a valid computer ID for IEM " after upgrade to 9.2.0.2

Usage and Config BFI
22

There an APAR for similar problem fixed in 9.1.1229.0

Another thread about the issue, maybe one of the reasons described there is affecting you:

23

does that mean that it isnā€™t actually fixed ?, or its hitting that problem in a different way?
should i consider applying that local fix mentioned in APAR on IEM server?

24

@skotla
Well APAR was fixed in more recent IEM version that you are using, but before you apply any fix.
Can you check if you are using proxy?

25

yes, proxies are configured for IEM server to access internet.

26

Can you make sure your configuration matches doc:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Proxy%20Server%20Settings

27

Maybe this is the problem: Make sure that the proxy is bypassed for internal network and component-to-component communications because this might cause problems with how the IBM Endpoint Manager server works and is inefficient for the proxy. Use the ProxyExceptionList setting, if needed, to exclude local systems from the communication through the proxy.

28

Ok sure, will go through it and get back to you. Thanks for your help on this so far.

29

I reviewed some older PMRs which seem to have same error problem and one that seems to match exactly your scenario was closed with resolution:

After removing export http_proxy from /etc/profile and following the documentation on Proxy config we now have successful connection.

1 Like
30

Thanks MIchal, now i am able to add new VM managers without any error.
with additional inputs from IBM PMR support, i modified /etc/init.d/beswebreports to added blank proxy lines and restarted the server, and that fixed the issue.

31

but my problem related original PMR 80898,082,000 " VM managers in pending state" continues to be there,
iā€™ve added a new VM manager , supplied all the necessary credentials and did a connection test.

connection test shows successful, but VM manager remains in pending state. it been over 12 hours since i added that VM manager.

32

Did you run import? Pending will stay until import is ran.

33

yes the import ran successful, but its still in pending state.

34

was there 12h+ gap between when you defined vmmanager and import?

35

yes, there was over 12h gap.
Vm manager was added and connection test was successful around 6:45 pm IST and scheduled import ran successful at 10:30 am IST.

36

Can you verify you have upload fixlet for vmman enabled?

37

is this the one :
6/3/2015 3:00:18 AM Open 100.00% (1/1) Upload VM Manager Tool Scan Results IBM License Reporting (ILMT) v9 IEMAdmin Single Action

i see it in open state.

i also see one more related fix , not sure if this needs to be run:
Force VM Manager Tool Scan Results Upload Low IBM License Reporting (ILMT) v9 1 / 1,716 0 Troubleshooting 284 KB IBM

38

@skotla
Did ā€œpendingā€ state resolve to OK ?

39

nope, its still in pending state.

40

@skotla
Ok, support will need to take care of this. I am out of ideas. Sorry I couldnā€™t be more helpful.

41

Hi all ā€¦

I just had this same problem on a Windows-based deployment of ILMT. My deployment is running ILMT 9.2.2 and BigFix 9.2.6.94 (the current releases as of this writing). ILMT and its SQL Server are on separate machines. BigFix and its SQL Server are also on separate machines. BigFix uses a proxy server to access the Internet.

Yesterday my client was able to add a single VM Manager on the VM Managers panel, and he tested it, and it was fine. Today when we tried to add a second VM Manager, we got the ā€œcould not get a valid computer idā€ message when we clicked the Add button. The same thing happened if we tried to edit the existing entry. We saw error 500 Internal Server Error in the tema.log file but not much else to go on.

What we found was that even though we could not manage the VM Managers, the VM Manager tool on the BigFix server was still running properly, connecting to vCenter, and weā€™d see the connection status change on the VM Managers panel. We simply could not add or modify VM Managers on this panel. (I didnā€™t want to delete the entry so we didnā€™t try deleting it).

I was able to resolve this issue by (believe it or not) rebooting all the servers. I probably didnā€™t have to reboot SQL Server but I did anyway. While I donā€™t know what happened or why this happened, this is my guess. The proxy definition was incorrectly removed by an administrator (besadmin.exe /setproxy /delete) and then put back, and for unknown reasons, ILMT was not able to read this updated configuration. Restarting the server refreshed this part of the configuration, so the VM Managers panel started working again. Again, this is only a guess.

Hope this helps someone with a Windows setup that experiences this issue.

ā€“Mark