update tools: Response code 403 errors

Am getting "Response code was 403" from several different sources. My service plan was registered almost a month ago, and I was not having any issue till about a week ago. I am able to log into the sunsolve and sunconnection sites, and am able to register (have redone this multiple times) successfully.

Using GUI Update Manager, on opening, I get message "Error: Unable to download document: "collection/default" Response code was 403"

Looking at Installed Patches, when I click on one that was installed recently, I get "Unable to download document: ReadMe/xxxxx-xx: Cannot Connect to Retrieve README-xxxxxx-xx Authentication failed due to bad credentials"

on command line, ran "smpatch analyze -@", and got "Failure: Response code was 403"

$ cat swupas.error.log

(empty)

$ cat swupas.log

Swup Agent run: Wed Dec 20 14:56:38 EST 2006

** DEBUG ON **

Attempt to get exclusive lock: 1

We have the lock!

prepare to register with Transport

Registration complete

Sleeping 90 secs...

OK, WE'RE AWAKE AGAIN!...

Updated last checkin time in CCR: 19444063

Number of swup server cmds to be executed: 0

smpatch collection name:current

need an analysis update: true

UpdateAnalysis: executing cmd: /usr/sbin/smpatch analyze -@ -C patchpro.patchset=current

UpdateAnalysis: cmd exit code: 1

UpdateAnalysis: cmd output: Failure: Response code was 403

Exiting for now...

Swup Agent finish: Wed Dec 20 14:58:24 EST 2006

*****END swupas.log*****

command "cctrunner -p" runs without incident.

It appears that I am no longer being authenticated by https://getupdates1.sun.com

When I go to sunconnection.sun.com, and log in, My system is there, and it is checking in, but am unable to select the system. Also, on the Summary page, it is not showing any update information, though I know there are updates that I have not installed.

Back at the Update Manager GUI, I am now getting authentication error even on startup of update manager. Have re-registered yet again, but without resolving the authentication problem.

Is this problem on my end, or is it on sunconnection.sun.com end? How can I resolve?

Thanks to all in advance,

Jace

[2305 byte] By [Jace444a] at [2007-11-26 13:17:36]
# 1
Hi.The support team aren't seeing any cases involving 403 errors, so I'm inclined to think there is either a configuration problem, or that there is an issue with your contract.Could you raise a case so that the support team can check your entitlement?Mod.
ForumModeratora at 2007-7-7 17:41:47 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2
Mod,What is correct method to raise a case so entitlement can be checked? I had called USA-4SUN yesterday, but they couldn't open a case for this issue.Thanks,Jace
Jace444a at 2007-7-7 17:41:48 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3
Hi.You should be able to raise a case on the product:'Sun Update Connection - System Edition'The case should then be assigned to the correct team.Mod.
ForumModeratora at 2007-7-7 17:41:48 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4
Thanks Mod. Have submitted a case. Will post back when have answer.Cheers!
Jace444a at 2007-7-7 17:41:48 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5

appears that GUI Update Manager's File->Manage Subscription is not actually "re-registering" the system. Solution was to:

# cacaoadm stop

# cacaoadm status

# /usr/lib/cc-ccr/bin/eraseCCRRepository

# rm /var/scn/persistence/SCN*

# reboot

Once logged-in (graphically), registration screen will appear. Fill out the information and updates are again available. Now just have to figure out what made my registration information go bad in the first place.

Cheers!

Jace

Jace444a at 2007-7-7 17:41:48 > top of Java-index,Administration Tools,Sun Update Connection-System...