Remko Weijnen's Blog (Remko's Blog)

About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like

Archive for March, 2011

After I uninstalled Office 2010 64 bit and installed Office 2010 32 bit I had a problem with Office Communicator 2007 R2.

After entering my password and clicking sign in it crashed every time:

image

In the EventLog an Application Error was recorded with some additional error info:

Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 10-3-2011 Time: 15:20:52 User: N/A Computer: remkolaptop Description: Faulting application name: communicator.exe, version: 3.5.6907.221, time stamp: 0x4cddcd9f Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa Exception code: 0xc06d007e Fault offset: 0x0000b727 Faulting process id: 0xf94 Faulting application start time: 0x01cbdf2e592fc53c Faulting application path: C:\Program Files (x86)\Microsoft Office Communicator\communicator.exe Faulting module path: C:\Windows\syswow64\KERNELBASE.dll Report Id: 9a4e3adf-4b21-11e0-8f0f-c0cb38a92f9b For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The exception code is 0xc06d007e which is defined in WINERROR.h as ERROR_MOD_NOT_FOUND, the error description is: “The specified module could not be found”.

(more…)

  • 0 Comments
  • Filed under: General
  • Office 2010 cannot remove registry key

    I have worked with Office 2010 x64 for a while now but because of compatibility issues I wanted to remove it and install the x86 version instead.

    After uninstall Office left a key in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Common\SmartTag\Actions\{B7EFF951-E52F-45CC-9EF7-57124F2177CC}

    I couldn’t remove it so I figured there was a specific process that had opened this key but couldn’t find anything (using Process Explorer).

    Then I checked the permissions on the Office key but it was set to Full Control for Administrators.
    (more…)

  • 9 Comments
  • Filed under: General
  • In the previous parts (part 1 part 2) i’ve described the theoretical part and implementation problems. So, now we can write the code:

    1) In case we login the user, we just call LsaLogonUser to get the token:
    (more…)

    In part 1 I’ve described the theoretical parts needed for a custom autologon application implementation.

    But there are some practical problems which I will describe here.

    1) I use the LsaLogonUser function to log in the user. However, if I do not pass not null for the LocalGroups parameter, msgina.dll fails to process the logon.

    Why? Because it looks for the SE_GROUP_LOGON_ID SID and treat it as logon SID. So we have to add the logon SID manually:
    (more…)

    Donate


    Blogroll


    Categories


    Archives