You cannot install the 64-bit version of Microsoft Access Database Engine 2010 because you currently have 32-bit Office products installed

Issue:

You cannot install the 64-bit version of Microsoft Access Database Engine 2010 because you currently have 32-bit Office products installed.

Cause:

Microsoft doesn’t allow side-by-side installation of Microsoft Office 32-bit and 64-bit.

Solution:

  1. Install from the command line using the passive switch
    AccessDatabaseEngine_x64.exe /passive
  2. Open the registry (regedit.exe)
  3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\FilesPaths
  4. Delete mso.dll

Notes:

If you don’t delete the mso.dll registry entry, Office will come up with Reconfiguring when opened.

System.Net.WebException: The request failed with HTTP status 503: Service Unavailable

Error:

Even though the Automatic Deployment Tool we use for downloading a deploying SCEP definitions was reporting as successfully, we noticed that servers did not have the latest antivirus definition installed.  When manually running a update in the SCEP client, it failed with the following:

Virus and spyware definitions update failed
Error code: 0x80244022
Error description: System Center Endpoint Protection couldn't install the definition updates. Please try again later.

WindowsUpdate.log

WARNING: There was an error communicating with the endpoint at 'HTTP://XXXXXX.DOMAIN.COM:8530/SimpleAuthWebService/SimpleAuth.asmx'.
WARNING: The server returned HTTP status code '503 (0x1F7)' with text 'Service Unavailable'.
WARNING: The service is temporarily overloaded.
WARNING: Web service call failed with hr = 80244022.

WCM.log

System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
Remote configuration failed on WSUS Server.

Solution:

  1. Open the IIS Manager console on the SCCM Primary server
  2. Under Connections, expand the server, and click on Application Pools
  3. You will see that the WsusPool application pool has stopped.
  4. Right-click WsusPool, and click on Advanced Settings…
  5. Scroll down to Recycling, set the value for Private Memory Limit (KB) to 4000000,and click OK
  6. Back at the Application Pool window, ensure WsusPool is still selected, and in the Actions pane, click Start

BSOD – The bugcheck was: 0x000000f4

Issue:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80bd3e09a0, 0xfffffa80bd3e0c80, 0xfffff80001dd3b60).

Solution:

Two XenApp 6.5 servers blue screened and rebooted one morning last week with the following:

MODULE_NAME: csrss
FAULTING_MODULE: 000000004a560000 csrss
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc115
PROCESS_OBJECT: fffffa80be232060
IMAGE_NAME: csrss.exe
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUCHECK_STRS: 0xF4
CURRENT_IRQL: 0

Luckily this happened only 4 weeks before, and after raising a job with Citrix they noted they could see that csrss.exe had an exception, however we only had Kernel Memory Dump enabled, so support could not find any information in the user space.  I enabled Complete Memory Dumps on the XenApp 6.5 desktop platform then.

Refer to the following article on how to change the dump level:
http://www.mhalliday.com/2015/10/15/configure-windows-server-to-enable-complete-memory-dumps/

We reopened the archived case, compressed, and uploaded the complete memory dump.

We received the response:

       From the dump we can see that Client/Server Runtime Subsystem process (csrss.exe) was terminated.
  • We do not see any of the Citrix modules involved in the thread call stack.
  • There was an exception while running sxs!BufferedStream::getLineBuf+0x1f
  • Microsoft’s SXS.DLL time stamp was Sat Nov 20 18:44:52 2010

We raised and logged a case with Microsoft.

What they came back with was:

Exception reported when handling sxs!BufferedStream::getLineBuf
_xxxxxpos variable is not allowed to be subtracted. This is how the exception happened.
 0x034 _lMarkedlinepos  : 0n-2025 <<<<<<<<< This value is negative

The solution from Microsoft was to install the following hotfix:

http://support.microsoft.com/kb/2675806/EN-US
2008R2_X64: http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix388736/7600/free/444247_intl_x64_zip.exe
2008_X64: http://hotfixv4.microsoft.com/Windows%20Vista/sp3/Fix399496/6000/free/446285_intl_x64_zip.exe
2008_X86: http://hotfixv4.microsoft.com/Windows%20Vista/sp3/Fix399496/6000/free/446284_intl_i386_zip.exe

Surprisingly, the issue is caused by click-once applications, in our case – Yammer.Notifier.exe

🙂

Remove Visibility of SCEP from XenApp Server

  1. Delete msseces.exe (SCEP GUI) from HKLM/Software/Microsoft/Windows/CurrentVersion/Run/MSC
    Explaination: Deleting msseces.exe from the location in the registry ensures that the SCEP GUI is not launched.
    Note: I’m not sure if this method is supported by Microsoft
  2. Delete SCEP icon in Start / All Programs
    Explaination: Removes icon so user cannot launch the SCEP GUI
  3. HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers\EPP
    Explanation: Removes Scan with System Center Endpoint Protection right-click on a drive
  4. HKEY_CLASSES_ROOT\Directory\shellex\ContextMenuHandlers\EPP
    Explanation: Removes Scan with System Center Endpoint Protection right-click on a Directory
  5. HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\EPP
    Explanation: Removes Scan with System Center Endpoint Protection right-click on a file
  6. Add msseces.exe to User Configuration / Policies / Administrative Templates / System / Policy in a GPO
    Explanation: This setting will restrict msseces.exe using Window Explorer
    Note: This will not stop users from being able to launch msseces.exe from the command line.  If someone knows how to resolve this, please post below!

Configure Windows Server to Enable Complete Memory Dumps

  1. Open registry (regedit) to open the registry editor.
  2. Set the ‘CrashDumpEnabled’ entry to 1.
    Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
    Value name: CrashDumpEnabled
    Type: REG_DWORD
    Value data: 1
  3. Set the ‘PagingFiles’ entry to enough to handle a dump.  On our XenApp bare metal servers, we have 131046MB total memory so that’s why we set the values to 132000.
    Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
    Value name: PagingFiles
    Type: REG_MULTI_SZ
    Value data: D:\pagefile.sys 132000 132000
  4. Restart the server to apply the changes.

Note: Since we use Citrix Provisioning Services (PVS) on our baremetal XenApp servers, we have a persistent D:\.  Anything on the operating system vDisk is restored to when the image was chaged to standard mode on reboot, so we ensure we point the page file, memory dumps, event logs (among other things) to D:\.  Since a complete dump is large, ensure there is enough space on D:\ or where you are writing to.

Click here to restore the language bar

Issue:

When opening a Citrix application, a pen appears in the system tray that says:

Click here to restore the language bar on <server>

Solution:

  1. Open regedit on the XenApp server where the application is published
  2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Citrix\wfshell\TWI
  3. Double-click SeamlessFlags (if the value doesn’t exist, create it as a DWORD)
  4. Set the value to Hex 0x00040000 or Decimal 262144