Anyone know CMS v11 Error 429? 2

[AvayaHelp]

On W XP, CMS v11 was working fine then today I try to boot it up and get the a dialog box with a red X and "error 429" I now I can't get back in. This happened once before on W2000 but all I did was reboot and then it was ok.

Anyone?

Avaya, Octel, AUDIX, CMS and other fun stuff.

"There is always a way, it may not be pretty but there is always a way."

&quot;I don't have a technical solution to your management problem.&quot; <PeaveyPhones>

P:-D

 

[RGarcia87]

Go into the CentreVu directory in your harddrive and look for the 'Cache' folder. Delete the cache file that is in there and try logging back in. If that doesn't work you need to uninstall the whole application and reinstall it. We had that trouble alot. View the readme file in the cd of after you reinstall it, it has something on that error.

 

[multibus2]

Upgrade the R3V11 Supervisor client to release FM.02, this version automatically deletes and re-creates the cache when the application is restarted.

 

[fwaneil]

'richgarcia87' Wrote

"Go into the CentreVu directory in your harddrive and look for the 'Cache' folder. Delete the cache file that is in there and try logging back in. If that doesn't work you need to uninstall the whole application and reinstall it. We had that trouble alot. View the readme file in the cd of after you reinstall it, it has something on that error."

If you get an 'unable to complete reqeust' error when you try to delete the 'cache' directory, go to task list (Ctrl-Alt-Del), under processes 'End Process' on a program called 'CVSTrans.exe', then delete the 'Cache' directory. the Cache files are supposed to clear out when the user shuts down CMS. The 'error 429' occurs when these files are not cleared out correctly. We also get a login screen with nothing but dashes, these steps will also fix this.

If CMS appears to be frozen (not updating, also try these steps.

Good Luck,

 

[RTMCKEE]

Actually this is not a cache problem. The cache issue usually shows itself as all "-" not just nothing where words should be.

Here is a link to the 429 fix.

http://support.avaya.com/japple/css...eID=157495&temp.bucketID=108020&PAGE=Document

RTMCKEE

PS. I just ran into this yesterday for the first time. I also just reinstalled the app, but it looks like there might be a better way.

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1

 

[AvayaHelp]

Thanks but we are now on version 12.

==========================================================
Does anyone have a quarter, I need to make a phone call?

 

[rdoranjr]

WOW,,,We just put in place all new PCs for our users. 6 of them are Supervisors where I had to install CMSv11. They are all getting this <429>Error. Never happened when they were on W2000 machines. They are now running XP.

Multibus,,,,how do I go about getting the FM.02 upgrade?

RTMckee,,,,I went to the AVAYA website (the one you gave the link to), and followed those instructions. It didn't work,,,

My next step is to try deleting the Cache folder

If anyone else has any ideas,,,please let me know

bob

 

[RTMCKEE]

Here is the link to download the latest rev of R11 Supervisor.

http://support.avaya.com/japple/css...eID=136406&temp.bucketID=108025&PAGE=Document

Interesting that the "fix" didnt work since the description seemed to match what i was seeing, but like I said, I didnt actually try the fix I ended up reinstalling the FN.02 update.

RTMCKEE

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1