PCM+ 4 after new patch, won't launch

[tschaps]

Hi, I am nearing the end of my 60 trial. And "trial" is a good word for it, followed by "and tribulations." However, I have purchased PCM+ and need to enter the license code in the next few days. HOWEVER, I don't think my problem is related to that, I included it just in case. I was notified that a patch was available for PCM+ 4, and it would gladly download and install it for me, and it would not require a restart-- fine and dandy. This is a 2008 R2 Server, fully updated, a few months old, plenty of RAM, etc.

After the update, I cannot start the PCM agent on the server anymore. It says "Core Components of the PCM Client have been updated by the server. You will need to relaunch the PCM Client for these changes to take effect." I click OK, and the client 'quits' (disappears, whatever). I restarted the server. I only use this client on this server, no other workstations. Google finds nothing, nothing apparently relevant in the Windows logs. 

Any ideas? I am really disappointed how much time I've wasted in the past six months with this new HP infrastructure and wireless chasing down stupid little problems. Along the same lines, I have been unable to get PCM+ to register my devices with HP, it says my username/password combo is bad. Yet I can login to all the HP sites with that Passport account, and I changed the password twice in an effort to get it to work, yet it won't. Am I expecting too much to think new HP software running on a new HP server managing a new HP wired and wireless infrastructure should be able to interact with the HP website? Is that expecting too much?

[RalphB]

With respect to the client/agent failure after the update, we have insufficient detail to understand the issue.   This is a challenging sort of issue to troubleshoot via the forum, so I recommend you open a trouble call with HPN Networking for this.

You can find the eSubmission and phone contact info for HP Networking Support from here:

http://h17007.www1.hp.com/us/en/contact/

for example:

https://h10145.www1.hp.com/help/Help_ContactInfo.aspx?cwp=2&SelectedTab=2  , then click the ">>" expander icon for your area in order to see the phone numbers.

and

https://h10145.www1.hp.com/help/help_questions.aspx?l2id=48&SelectedTab=3  for eSubmission.

The problem that you described in your third paragraph is in the HPN licensing portal and HPN is working on a fix.   The fix will be in the Portal itself, so users will not need to install a PCM update in order to get the fix.   HPN estimates that this will be fixed some time next week.

[tschaps]

I don't think it hurts to ask in a user forum whether anyone else has experienced the same problem to either get a solution someone else already found, or to add data points to the issue to possibly assist in finding a solution.

So I leave the question open until I have time to contact HP in the hopes I won't have to.

Thx

[RalphB]

Of course, you're right: it doesn't hurt to ask the user community.

[sfv]

i've got the same problem after update on 04.00.01.196_PCM-Software-0400-update1-win64.

Where can I find the patch???

[BelhassenBC]

We fixed the issue by simply re-Installing the client on the machine.

Pretty obvious when you see the error message : "Core Components of the PCM Client have been updated by the server. You will need to relaunch the PCM Client for these changes to take effect"

[tschaps]

---

@BelhassenBC wrote:

We fixed the issue by simply re-Installing the client on the machine.

Pretty obvious when you see the error message : "Core Components of the PCM Client have been updated by the server. You will need to relaunch the PCM Client for these changes to take effect"

---

You use your first post on this forum to write something snarky like that in a month-old thread? The only thing "pretty obvious" is that I would have tried "simply" reinstalling the client. But I also installed the client on two other computers and got the same message. I uninstalled the whole thing from the server and reinstalled, same message again.

So I put PCM on the back burner to wait for a day I can waste more time on it. Right now, I simply regret not going with the Cisco bid on our recent infrastructure project. HP Networking has just been a pain to deal with. They're not Procurve anymore.

[Chris Augustine]

I know this thread is a few months old, but I ran into the same issue.  My problem was due to another engineer that left himself logged into PCM on the server in an RDC session.  I had him log back in and launch PCM and the client updated.  Then I could login with any other user.

I don't know know if it had any thing to do with it but he also installed PCM under his windows account.

[cjonger]

I logged in as local administrator on the server and restartet the PCM Client twice, that made it work

[shewin]

Thanks.  Logging in as the domain administrator and lauching twice fixed my problem with the client.