My problem has repeatedly been that my account gets "deactiviated", and I have had to go through this at least 3 times in the last 4 months, with have a valid Platinum support contract.
Pretty depressing that there are this many issues. On Thu, May 28, 2009 at 3:28 PM, French, David <[email protected]> wrote: > You may also want to try adding --ssprot=http if using the latest > versions of pca. I discovered for my setup that using https will fail > downloading a lot of patches, but as soon as I use --ssprot=http > everything is much more reliable. In fact once last weekend everything > was failing using https, but worked perfectly when switched to http. > And yes, https had worked before. > > Anyway, just a thought... > > --Dave > >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Scott Severtson >> Sent: Thursday, May 28, 2009 7:34 AM >> To: PCA (Patch Check Advanced) Discussion >> Subject: Re: [pca] SunSolve: 403 Forbidden with valid Contract >> >> We've used PCA successfully in the past with this SunSolve account. >> >> However, I discovered yesterday that my contract number was >> no longer associated with the account for some reason. I've >> added the contract back in, but given your confirmation, I'm >> wondering if it may be an account configuration issue. >> >> I'll follow up with Sun for now. >> >> Thanks! >> --Scott >> >> >> On Thu, 2009-05-28 at 16:08 +0200, Martin Paul wrote: >> > Scott Severtson wrote: >> > > Via the SunSolve web site, I'm able to download patches >> that require >> > > a contract, but via PCA/wget, I'm seeing a 403: Forbidden. >> > >> > Is this a new problem, ie. has it worked before, or is it the first >> > time you're using pca to download patches? >> > >> > If you have special characters in your password, try to put >> it into a >> > configuration file instead of specifying it on the command line, or >> > quote correctly. >> > >> > > Is anyone else experiencing this? Is this an issue at Sun's end? >> > >> > I just tried, and it worked for me. Can you post the debug output >> > anyway (remove/overwrite the "Authorization: Basic XXX" setting), >> > maybe we can spot something. >> > >> > Martin. >> > >> >> > >
