Microsoft Outlook kan ikke startes. Outlook-vinduet kan ikke åbnes. Mappesættet kan ikke åbnes. Du skal have forbindelse til Microsoft Exchange med den aktuelle profil, før du kan synkronisere mapperne med Outlook-datafilen (.ost).


Fejlen ovenfor giver også fejl i eventlog med event ID 9646 (source: MSExchangeIS):

"Mapi session /o=XX AS/ou=XX/cn=Recipients/cn=XX with client type MoMT exceeded the maximum of 32 objects of type Session."

Jeg har revet mig i håret over denne fejl og samtidig betalt konsulenter i 3 timer for at finde løsningen på fejlen ovenfor - men de gav op. Brugeren med fejlen kunne åbne Outlook på egen PC, men ved opsætning af ny PC med Outlook, dukker fejlen op hos tilfældige brugere.

Endelig fandt jeg løsningen, som skulle rettes på Exchange serveren (vi anvender Exchange 2013, men så vidt jeg kan læse mig til, så virker det også på Exchange 2003, Exchange 2007 og Exchange 2010):

Det viser sig, at antallet af samtidige sessioner på Exchange serveren er overskredet. Løsningen for mig var at oprette denne nøgle i registreringsdatabasen på serveren og genstarte serveren (eller blot Microsoft Exchange Information Store service (MSExchangeIS)):



Kommentarer

Send en kommentar

Populære opslag fra denne blog

Microsoft Office 2016 and the AUTO_ACTIVATE property

Billede
In Office 2013 is was possible to automatically activate it after install by using a property called AUTO_ACTIVATE in the Office Customization Tool (OCT) (to start the OCT, you just need to run the setup for the Office installation like this: 'setup.exe /admin' - you don't need to download the OCT). It doesn't work in Office 2016. I solved it by running the OCT and doing this instead: If you want to know how the make the install completely automated, read on: I modified these settings: Save the .MSP file in the Office installation folder under \updates\. All .MSP files in this folder, is used during installation. If files exist in this folder, and you run setup.exe, the 'normal' Office installation will use the settings under \updates\ (the settings modified in the .MSP file created in OCT).
Læs mere

Disable logon and logoff events (event id 4624, 4625, 4634 (and all the other ones...))

I have tried several times to make my domain controller not log logon and logoff events in the security log. But it seems to ignore the settings in the domain controller group policy. I now use Auditpol in stead - that works (thanks Morgan J ): To disable all logon and logoff messages in the security log use (in an elevated command prompt): auditpol /set /category:"Logon/Logoff" /success:disable & auditpol /set /category:"Logon/Logoff" /failure:disable It is also possible to just disable the logon messages by using the subcategory switch: auditpol /set /subcategory:"Logon" /success:disable & auditpol /set /subcategory:"Logon" /failure:disable To view the current settings, run: auditpol /get /category:*
Læs mere

Enable OpenELEC SSH login with keys, and without password, disable local SSH password

1) Connect to OpenELEC using ordinary SSH with user 'root' and password 'openelec' 2) Change directory to .ssh/: cd .ssh/ 3) Generate a pair of ssh keys: ssh-keygen -t rsa Accept all default settings by pressing [ENTER]. If you are asked to to overwrite id_rsa press 'y' and [ENTER]. 4) Copy the content of the public key ('id_rsa.pub') into 'authorized_keys': cat id_rsa.pub >> authorized_keys 5) Copy 'id_rsa' to the device that you want to log into OpenELEC from, e.g. your mobile phone. 6) Setup the connection on your device using the private key ('id_rsa'). You still need to use the username 'root'. You can rename this file and give it a more useful name. Make sure that you are able to log in without using the password! 7) To disable the local password on OpenELEC/KODI, open settings in KODI and select "Services" on the left hand side. Here you can disable SSH password.
Læs mere