For 7.6 there should be a hotfix for this already, for 8.0 wait until july 9 for SP4.
Thank you Bill, I have seen that it could be a problem between internet
explorer and the sun site, so I tried downloading the latest version of
July 5 of the patchdiag.xref by myself with mozila and then put it on
the server replacing the original, then I TURNED OFF THE DOWNLOAD PATCH
DIAG flag and it works, I will try replacing the explorer.
I appreciate your help.
IHAC that is experiencing issues between BL and their proxy since the latest sun change. You using a proxy?
No I don´t, but I'm agree that it is happening since the latest change
in sun site
Incidentally I'm having the same issue. Except I'm doing a new installation of BladeLogic at our site. I've opened a case with Support on this
issue, but not gotten a response back yet. I've looked through the users guide for the manual procedure, but haven't tried it yet. When the blade software downloads the patchdiag.xref it's not getting what it expects at all. Sun/Oracle have defintely changed things up. Is it confirmed fixed in SP4?
There were 2 issues w/ this typically:
1 - you need to log into your sun solve acct and allow for automated downloads, (bmc) support should have info on this
2 - sp4 should fix the recent solaris download issues, though I thought that was only for the actual patch payloads as patchdiag.xref is not passwd protected.
The other things to look at are:
1 - do you have outbound access to the sunsolve site from the appserver
2 - is there any proxy or firewall blocking on the user-agent (what the 'browser' shows up as)
Correct, support said install SP4 available Friday. We are going to install it on Monday and see what happens.
I was having the same problem in BL 8.1 SP4.
I was getting the same error " Unable to get the date of patchdiag.xref".
This is because of some syntactical issue in xref file which BL is not able to recognize properly.
Can you provide your xref file which you are using or can you provide the initial lines from xref file ?