topic Re: Your Office configuration is corrupt. Reinstall Cisco Jabber in Collaboration Applications

Your Office configuration is corrupt. Reinstall Cisco Jabber to restore Office Integration - Error code: CJ:1000:101

skirk1983 — Sun, 17 Mar 2019 22:10:09 GMT

Hi all

I've just installed the offically release of J4W 9.2 build 496 on a few clients. When the Jabber clients starts, we are seeing a error message in the yellow triangle.

"Your Office configuration is corrupt. Reinstall Cisco Jabber to restore Office Integration" Error code: CJ:1000:101

However, the integration is still working, but its annoying for the users. Its seem only affects users without admin privileges.

Any fix for this? Reinstall of Jabber or a restart of the computer dosen't fix it.

Windows 7 Enterprise 32 bit.

Office 2010 32 bit.

PRT file is attached.

Best regards

Your Office configuration is corrupt. Reinstall Cisco Jabber to

leslie-meade — Mon, 15 Apr 2013 18:19:12 GMT

By chance are your users IM only ?

I have this issue with IM and Jabber users, but if I reboot the Jabber users machines the error will change to Jabber has repaired, and it will not show again...

IM users will get this error all the time

Your Office configuration is corrupt. Reinstall Cisco Jabber to

skirk1983 — Tue, 16 Apr 2013 06:56:34 GMT

Hi Leslie

No my Jabber clients are using IM and Phone functionality.

Here is a copy of our config file:

EDI

OU=xxxxx,DC=xxxxx,dc=xxxxx,DC=com

otherHomePhone

true

sAMAccountName

http://www.xxxxxxx.com/~/media/sAMAccountName.jpg

+XXXXXX|+## #### ####|+XXXXXX|+## #### ####

audio

true

false

.exe;.msi;.rar;.zip;.mp3

false

presence

phone

It doesn''t help and reboot the computer. No problems in 9.1.X and in 9.2 beta.

Any fix?

Your Office configuration is corrupt. Reinstall Cisco Jabber to

Christos Georgiadis — Tue, 16 Apr 2013 10:47:02 GMT

Hi Kristian,

This is currently under investigation from TAC so bear with us. I will update when I have more on it.

Thanks,
Christos

Your Office configuration is corrupt. Reinstall Cisco Jabber to

David28 — Thu, 18 Apr 2013 06:57:56 GMT

Hi,

any update on this from TAC?

My customer is facing the same problem.

regards, Dave

Your Office configuration is corrupt. Reinstall Cisco Jabber to

Christos Georgiadis — Thu, 18 Apr 2013 08:08:05 GMT

Not yet but I will update you guys once we find out the details.

Regards,

Christos

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

Christos Georgiadis — Fri, 19 Apr 2013 13:19:05 GMT

Hi all,

I have done some tests in the lab. I managed to reproduce, fix it and then break it again so I am confident that we can clear this error.

From the logs I see the error is due to this

2013-04-16 12:09:09,437 ERROR [0x00001250] [xplugin\Click2XLifecycleManager.cpp(380)] [plugin-runtime] [OpenRegistryKey] - Failed to open Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu in 80000001 use64Bit: 0

2013-04-16 12:09:09,437 ERROR [0x00001250] [xplugin\Click2XLifecycleManager.cpp(351)] [plugin-runtime] [CreateRegistryKey] - Failed to create Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu in 80000001 use64Bit: 0

In the affected PC's this registry path doesn't exist or it doesn't have the correct values.

So what you can do is this

-- On a PC where you don't get this error go to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu

-- Export the folder (PersonaMenu) to a file

-- On the affected PC's take a backup of the registry (always recommended as a precaution)

-- Import the reg file to the registry

This is the workaround I have found. The defect that tracks this issue is CSCug43138

Let me know if that works or not

HTH,

Christos

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

matthewglennford — Fri, 19 Apr 2013 17:56:44 GMT

We also have this issue after a Group Policy based, ORCA packaged rollout, upgrading from 9.1.3. I'll try to take some time today or tomorrow to try the registry key workaround.

Edit; we are also all x86 installs for Office and Windows 7 Enterprise.

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

Scott_A_A — Tue, 23 Apr 2013 22:39:05 GMT

I would think that an ADM/ADMx provided by Cisco would resolve this issue given the application is trying to write to the Policies key in the user's registry hive. Especially when one of the suggestions is to deploy via Group Policy!

In a domain environment this area is locked by default via global policy. The reason you are getting the error is becasuse Jabber is trying to create a D_WORD value called TagContact under HKCU\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu and can't becasuse by default the user doesn't have rights to this part of their registry hive. Hence the error.

For a test just create the required keys in the user hive. (MAKE SURE JABBER IS LOGGED OFF AND CLOSED)

Option 1. Create a D_WORD value called TagContact with a value of '0' under HKCU\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu. Open Jabber and log in to confirm the error is gone.

Option 2. Alternatively you can create a key called 14.0 under HKCU\Software\Policies\Microsoft\Office and then modify the permissions on the 14.0 key to give the user full rights. You will also need to go into the 'Advanced Settings' tab and tick the box to 'Replace all child objects with inherritable permissions from this object'. Open Jabber again and then log in. The message should have dissappeared by now. If not, check the permissions on the 14.0 folder under Office and try again.

If Cisco are reccommending Group Policy as a method of deployment then they should have provided an ADM/ADMX so this can be set via domain policy. Simply providing end users with a reg key as a work around is pretty unprofessiuonal.

Can you guys please provide an ADM/ADMx for global deployments please?

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

leslie-meade — Tue, 23 Apr 2013 22:43:08 GMT

So i has also exported the keys from a worknig version and imported to a non working one and its still not working.

Althou I am not the windows admin team here..

I will get them to have a look at the above comment and take it from there

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

Scott_A_A — Tue, 23 Apr 2013 22:53:40 GMT

Leslie, if you imported the key from another user it is in all liklihood be because you still cannot write to the registry. The workaround from Cisco is to import the following data into your registry.

As a test copy all the text in italics below and paste it into notepad. Save the file as Jabber.reg. Double click on the Jabber.reg file (You can right click on the file and seelect Merge). Click OK on any message to allow the merge to continue. You need to exit out of Jabber before doing this. If you get an error when merging this data then you won't have sufficient rights to the registry hive. Can you let me know the results.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu]
"TagContact"=dword:00000000
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\IM]
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

leslie-meade — Tue, 23 Apr 2013 22:57:28 GMT

Thanks for the info.. I have passed it onto the Windows team to test..

I will get back to you asap

thanks for your help

Your Office configuration is corrupt. Reinstall Cisco Jabber to

matthewglennford — Thu, 25 Apr 2013 16:25:04 GMT

Scott Alchin wrote:
Leslie, if you imported the key from another user it is in all liklihood be because you still cannot write to the registry. The workaround from Cisco is to import the following data into your registry. 
As a test copy all the text in italics below and paste it into notepad. Save the file as Jabber.reg. Double click on the Jabber.reg file (You can right click on the file and seelect Merge). Click OK on any message to allow the merge to continue. You need to exit out of Jabber before doing this. If you get an error when merging this data then you won't have sufficient rights to the registry hive. Can you let me know the results.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0]
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common]
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu]
"TagContact"=dword:00000000
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\IM]
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

Yup - worked here. x86 Win7 and Ofice 2010.

Your Office configuration is corrupt. Reinstall Cisco Jabber to

matt.woodling — Fri, 26 Apr 2013 16:33:45 GMT

This fix did not work for me. I exited Jabber and Outlook, applied the registry changes with no errors, started Outlook, started Jabber and still get the alert. We are using Jabber IM and phone integration.

Your Office configuration is corrupt. Reinstall Cisco Jabber to

Scott_A_A — Mon, 29 Apr 2013 01:25:54 GMT

Matt, I notice after Jabber runs it's also trying to create a 12.0 key under the office key with the same values as the 14.0 keys. Can you copy the italics into notepad and save it with a .reg extension and then merge it to see if it clears the message. It's only a workaround and doesn't guarantee success. If it fails again you may need to check the permissions of both the office 12.0 and 14.0 keys for your account because you need the rights to modify at the very minimum.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Common]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Common\PersonaMenu]
"TagContact"=dword:00000000
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\IM]
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

Why the app is trying to create keys without interrogating for the version of office installed is a mystery. We still run office 2003 (11.0) yet Jabber is creating office keys for both 2007 and 2010. It isn't looking to see if these versions of office are installed it's just creating these keys regardless. It's hard to blame Microsoft when Jabber is just creating keys without even interrogating the installed version. The developers may need to rethink how the application integrates because the key creation should be based on version installed and write the keys accordingly, not just create keys to cover the last two office suites.

The way it's configured at the moment, users require access to the registry to create modify keys under the policies directory for office 2007 and office 2010 whether they exist or not! If it really needs to create these keys then Cisco need to supply an ADM/ADMx because it's trying to modify keys controlled by Group Policy.

Let me know how it goes.

Your Office configuration is corrupt. Reinstall Cisco Jabber to

sobeking — Thu, 02 May 2013 03:16:28 GMT

I'm also experiencing the same problem. XP/Win7 and Office 2007 / 2010. Also Updating [HKEY_CURRENT_USER
doesn't work, you'll have go to the Registry HKEY_USER//... same path as above.

Hopefully there will be an update soon.

--C

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

skirk1983 — Thu, 02 May 2013 08:58:25 GMT

When do we see a permanent fix for this?

Why was J4W 9.2 released with such a bug? The ver EAP Drop 2 version, did not have this issue.

I can't deploy 9.2 before we have a fix

/Kristian

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

jeff.makowski — Thu, 02 May 2013 16:42:02 GMT

Currently Being Moderated

Apr 23, 2013 4:53 PM (in response to leslie-meade)

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber to restore Office Integration - Error code: CJ:1000:101

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu]
"TagContact"=dword:00000000
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\IM]
"EnablePresence"="2"
"SetOnlineStatusLevel"="2"

I used these settings on my clients and the error goes away. To publish these to all users I'm using Microsoft Group Policy Preferences to create the registry entries.

http://technet.microsoft.com/en-us/library/cc753092.aspx

Win 7 Pro 32-bit

Office 2010 32-bit

Your Office configuration is corrupt. Reinstall Cisco Jabber to

keithknowles — Thu, 02 May 2013 17:00:36 GMT

I was able to fix this by fully exiting Jabber and MS Office apps, then right-clicking Jabber and selecting "Run as Administrator". There was another error indicator telling me that it was fixing the Office Integration. I fully exited Jabber and then on subsequent launches of Jabber (not as Administrator) it works just fine. I have also noticed that Cisco Media Servies reports as not functioning unless Run as Administrator, though it does appear to work regardless.

Re: Your Office configuration is corrupt. Reinstall Cisco Jabber

Scott_A_A — Fri, 03 May 2013 00:42:06 GMT

I've found another issue I'd suggest is a bug. If you have a communiuty or 'shared resource' PC that multiple users can access using the same login) then you have an issue if you're using Jabber because the Outlook calendar sync feature of Jabber will sync with the account logged into the local PC, not the account logged into Jabber.

For some this may not be an issue but we have library staff that use shared consoles when they are serving at the front counter. They log into all their front counter (customer facing) workstations using a generic login, not their own login. Sadly if you are logged into one of these workstations with a generic login, e.g. LIBRARYUSER and then log into Jabber with your normal company logon, e.g. COMPANYUSER then Jabber won't give you the calendar for COMPANYUSER, instead it sync's with the calendar of the account logged onto the workstation, e.g. LIBRARYUSER, when really it should be sync'd with your AD Exchange mailbox. Poor, very poor.

I would have thought that part of the PRESENCE configuration would be for the Jabber client to sync the account authenticated to Presence with their Exchange account. LDAP anyone.....

As for the error, if you aren't using office 2007 or 2010 and unless Cisco say otherwise then the 12.0 and 14.0 registry keys under HKCU\Software\Policies\Microsoft\Office are basically redundant. I modified our deployment package so that the 12.0 and 14.0 keys do not get deployed. I've done this in the MST for a test and don't get any issues. The initial error is still there but then it is gone the next time you authenticate.

P.S. Running Procmon shows a lot of Access Denied errors trying to enumerate driver sets (HKLM) when you log into Jabber.