Skype Outlook Add-in keeps being disabled

Thanks to : https://www.outlook-apps.com/inactive-outlook-add-ins/

For me it was sufficient to do the following:

1) Close Outlook.
2) Remove the key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Resiliency\DisabledItems. Find the one which links to UCAddin.dll and remove it.
3) Start Outlook again.
4) Enable the Add-in like File -> Options -> Add Ins -> Go -> Check the Skype Add in. (The Load Behaviour should say "Load at startup" now.

Kommentare

Beliebte Posts aus diesem Blog

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc)

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) pdadmin sec_master> user create dg1234 uid=dg1234,cn=team1,cn=users,o=company lala lala ********** Could not perform the administration request Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) Description: After the upgrade from Policy Director (policy server) V5.1 to V6.0 the errors above occured when trying to write to the registry. Solution: The task of updating the ldap schema did not work well for some reason. After doing it again the errors did not occur again: # ivrgy_tool -d -h ldap_host -p port -D ldap_admin -w pwd schema

WebSphere Application Server LDAP: The administrative user ID does not exist in the user repository.

When you try to enable global security with ldap authentication you get the following error when configuring your ldap repository (IBM Directory Server): The administrative user ID does not exist in the user repository. Reason: The bind user must be searchable. This means that an ldapsearch with this user as bind user must return his own entry. If this does not work, you have to add an aclEntry: vi change-was7101-aclentry.ldif dn: uid=was7101,cn=mygroup,cn=admusr,o=mycomp aclentry: access-id:UID=WAS7101,CN=MYGROUP,CN=ADMUSR,O=MYCOMP:normal:rsc $ ldapmodify -h myhost -x -D "cn=root" -w ******* -f change-was7101-aclentry.ldif modifying entry "uid=was7101,cn=mygroup,cn=admusr,o=mycomp" Now user was7101 can do an ldapsearch to find itself and therefore you can use it to configure you LDAP repository. This article gave me the hint: http://www-01.ibm.com/support/docview.wss?rs=767&uid=swg21219253

HPDAZ0602E Corrupted file: Insufficient information to contact a Policy Server.

Problem [root@srv1234 PolicyDirector]# java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ******** -appsvr_id tim2tam -appsvr_pwd secret -host srv1234 -mode remote -port 999 -policysvr srv1235.mycompany.com:7135:1 -authzsvr srv1235.mycompany.com:7136:1 -cfg_file /opt/PolicyDirector/conf/srv1235.conf -key_file /opt/PolicyDirector/conf/keystore_srv1235.ks -domain Default -cfg_action create Exception in thread "main" [java.lang.IllegalStateException: HPDAZ0602E Corrupted file: Insufficient information to contact a Policy Server. ] Wrappered Exception: java.lang.IllegalStateException: HPDAZ0602E Corrupted file: Insufficient information to contact a Policy Server. at com.tivoli.pd.jadmin.PDAppSvrConfig.configureAppSvr(PDAppSvrConfig.java:195) at com.tivoli.pd.jcfg.SvrSslCfg.config(SvrSslCfg.java:179) ...

Dani's Middleware

Dieses Blog durchsuchen