MS Excel: C:\Windows\System32\SGXLADDIN.DLL

SGXLADDIN.DLL could not be found Error

ERROR: C:\Windows\System32\SGXLADDIN.DLL could not be found.

 

This error occurs when you launch Microsoft Excel 2007, 2003 or 2002 following the installation and subsequent uninstallation of a Sage product such as Sage Line 50 Accounts & Sage Instant Accounts.

 

When a number of Sage products are installed they also install a Microsoft Office Addin file called SGXLADDIN.DLL which provides integration between Microsoft Excel and the Sage product however when uninstalling certain Sage products the addin reference is left inside Excel but the file is removed, hence the error.

 

Luckily, this one is very simple to fix.  Read on.

 

 

Solution 1: Microsoft Office 2007 Users:

  1. Open Microsoft Excel
  2. Click the Microsoft Office button (that’s the large ugly button in the top left hand corner)
  3. Click Excel Options button at the bottom right of the menu
  4. Click Add-ins in the left hand navigator
  5. Now in the right hand pane, click the Manage Add-ins button at the bottom – the Add-ins dialog should appear.
  6. Clear the checkbox next to the add-in that reads SGXLADDIN.DLL
  7. Click OK and restart Excel

 

Solution 2: Microsoft Office 2003 & lower Users:

  1. Open Microsoft Excel
  2. Click Tools > Add-ins…
  3. Clear the checkbox next to the add-in that reads SGXLADDIN.DLL
  4. Click OK and restart Excel

Office 2003: Cannot Empty The Clipboard Error Message

ms office 2003 error cannot empty clipboardCannot Empty The Clipboard

There are a multitude of explanations out there as to why this error appears but thus far I have only experienced this error for one reason and it’s very specific.

 

I connect to a Windows 2003 Server through Remote Desktop Connection and the next time I attempt to do a copy or cut & paste operation in Excel or Word I receive the error message:  Cannot empty the Clipboard as displayed in the above screenshot.<!– ckey=”35103946″ –>

 

I have never received this error for the following reasons (as alleged by many other websites):

  • Auto calc not on
  • User error
  • Windows Clipboard Viewer
  • Download Managers
  • Pixie Dust or Gremlins 🙂

This article briefly explains exactly what conditions this error occurs under and provides you with two solutions.  One is a temporary solution and one is more permanent.

 

It depends on the level of access you have to the Windows 2003 Server that you are accessing via Remote Desktop Connection (RDC) as to which solution you want or can use.

Explanation:

So briefly, when you connect to Windows 2003 Server via Windows Remote Desktop Connection your Windows Clipboard gets shared with the session that you create on the Terminal Server.  This process is managed on the server by a file named rdpclip.exe.  It is this file that is causing the problem.

 

Solution 1 (Temporary):

This solution is temporary and the problem is likely to return the next time you create a new session through RDC.

  1. Close all Microsoft Office programs that you currently have open on your local system.
  2. Open your Remote Desktop session on the Windows 2003 Server and close any open programs
  3. Right click on the taskbar and click Task Manager
    Cannot Empty Clipboard
  4. Click the Processes tab and then click the first column to sort the processes alphabetically
  5. Locate the process rdpclip.exe and click it to highlight it
  6. Click End Process buton
  7. In the next warning dialog, click Yes
  8. Now minimize your Remote Desktop session
  9. On your local system, start Microsoft Excel and test the copy/paste function

 

Solution 2:

This solution is more permanent but it requires you to have the access and confidence to install Microsoft hotfixes on the Windows 2003 Server and you’ll also need to reboot the server when you’re finished installing.

  1. Ensure you meet the following requirements:
    • Windows 2003 Server
    • x86 (for ia64 visit microsoft.com)
    • Service Pack 1 installed
  2. Download the hotfix here
  3. Install the hotfix on the Windows 2003 Server system
  4. Reboot the system and reconnect via Remote Desktop Connection