We Keep Coding

mso20win32client.dll error when initializing new_RDOSession

I am getting errors in event viewer every time my application runs this line:
Redemption.RDOSession rSession = RedemptionLoader.new_RDOSession();
event viewer error:
faulting application name: (my.exe)
exception code: 0xc0000005
faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
The oddest part is that it proceeds to create the session and makes it to the end of my code if I let it, successfully looking up an email in Outlook. This is in production and has worked for years, but for some months now it has been racking up the same error in Event Viewer. End users don't notice, but IT is seeing thousands of errors now which makes it hard for them to know when other problems might be showing up.
I reproduced this on the first try with:
Windows 10 Home, OS build 19044.1706, Windows Feature Experience Pack 120.2212.4170.0
Outlook: Microsoft® Outlook® for Microsoft 365 MSO (Version 2205 Build 16.0.15225.20172) 64-bit
I added logging in my CS code to make sure this caused the error. The error occurs if set ignoreoutlook to "e", and not if I set it to "d":
Microsoft.Office.Interop.Outlook.Application oApp = (Application)Marshal.GetActiveObject("Outlook.Application");
if (ignoreoutlook.Equals("d")) return;
Redemption.RDOSession rSession = RedemptionLoader.new_RDOSession(); // new Redemption.RDOSession();
if (ignoreoutlook.Equals("e")) return;
As for:
C:\ProgramFiles\Common Files\Microsoft Shared\Office16\mso20win32client.dll
it doesn't exist. There is a dll of that name in both:
C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE16
C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16
If Redemption wants to use that dll, how is it working without it?
Is there a way to configure Redemption to skip that dll and move on to whatever else it must be doing to get it to work after that error?

There are quite a few things going on once the MAPI system (when Redemption loads it and calls MAPIInitialize) initializes common Office runtime, which has a bunch of its own problems, since it loads telemetry and licensing. Some of that functionlity only works when running inside the (virtualized) Office app environment (it patches a few Win API functions etc.)
Check if you see the same problem in MFCMAPI if you log to a profile (to ensure the MAPI system is loaded). If you do, that means the problem is in the MAPI system and you can work with MS support. If not, something is specific to your app.
One thing to keep in mind is that your app must embed a manifest and advertise its support for Windows 10. Otherwise common Office run-time tries to patch wrong Win API functions.

Exception thrown using VS publish on 1 developers machine

When deploying 1 application through Visual Studio 2017 & 2015 one of our devs is getting the exception below raised in the servers event logs.
No other developer gets this exception, and it seems to happen for all apps that developer tries to deploy.
Here's what the log says about it on the server ...
The description for Event ID 1 from source Web Deploy cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
User: S0000878\WROW
Client IP: 10.100.177.100:80
Content-Type: application/msdeploy
Version: 9.0.0.0
MSDeploy.VersionMin: 7.1.600.0
MSDeploy.VersionMax: 9.0.1972.0
MSDeploy.Method: Sync
MSDeploy.RequestId: 94589097-54ba-4753-a37b-32571bfe6b8f
MSDeploy.RequestCulture: en-GB
MSDeploy.RequestUICulture: en-GB
ServerVersion: 9.0.1962.0
Skip: objectName="^configProtectedData$"
Provider: auto, Path:
A tracing deployment agent exception occurred that was propagated to the client. Request ID '94589097-54ba-4753-a37b-32571bfe6b8f'. Request Timestamp: '16/05/2017 10:26:59'. Error Details:
System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
at System.IO.BinaryReader.FillBuffer(Int32 numBytes)
at System.IO.BinaryReader.ReadInt16()
at Microsoft.Web.Deployment.PackageDeserializer.GetNextEntryType()
at Microsoft.Web.Deployment.SerializationProvider..ctor(DeploymentBaseContext baseContext, PackageDeserializer deserializer)
at Microsoft.Web.Deployment.PackageDeserializer.GetSerializationProvider()
at Microsoft.Web.Deployment.DeploymentAgent.HandleSync(DeploymentAgentAsyncData asyncData, Nullable`1 passId, String user, String siteName)
at Microsoft.Web.Deployment.DeploymentAgent.HandleRequestWorker(DeploymentAgentAsyncData asyncData)
at Microsoft.Web.Deployment.DeploymentAgent.HandleRequest(DeploymentAgentAsyncData asyncData)
I'm at a loss because the deployment process works from all other dev machines and from our build boxes, and yet it's only the server that complains.
What should I be looking for on the developers machine that might help indicate the real problem here?

It seems that the problem was caused by proxy settings on the developers machine.
this sort of problem can be caused by tools like Fiddler (often used by developers to debug API calls to web services).
The developer seems to have fixed it by repairing VS in this instance suggesting that there was also an issue with the VS install.

In my case, the issue was caused by a security software in our environment. However, while doing research about this issue, I noticed that these are also required for Web Deploy to work:
Management Services should be installed (Add Role and Features > Web
Server)
Web Management Service sand Web Deploy Agent Service hould be
running
Make sure Fiddler or any other similar software is not
running while publishing
Make sure TCP port 8172 is open in the
server
Source: Web Deploy experienced a connection problem (ERROR_CONNECTION_TERMINATED)

Upgrading wp8 to wp8.1 silverlight, debugger cannot be launched

I have now had an error with VS2013 and WP8.1 silverlight for a couple of days.
I get a couple of different errors, ..Ensure unlocked screen.., AgHost.exe could not be launched, port is in use by another program and ensure the device is unlocked.
These errors came suddenly after I retarged the solution. I have no compiling errors.
Solution Attempts
Restart PC
Restart program
unregister and reregister the phone
reinstall Update 3
reinstall VS2013
Windows Phone 8 Application crash once its launched AgHost.exe' has exited with code -532265403
Install VS2015 with no luck.
reinstall VS2013 Update 4
Nothing worked. The error is also the same for emulator as well as different devices. I can however get the release mode installed. Break points can be used when using release mode, but I have to Clean, Rebuild and then deploy for every time I want to deploy the application. Further the deploy time has gone up exponentially. Before upgrading I used a maximum of 10 seconds. Now it is above a minute in wait time. :/
Anyone has a solution for this ?
Extra
If I run the solution before upgrade on device or Emulator It spins up with debugger. If then go to the updated WP81, I get a popup with info Something is taking longer then normal and then it crashes with ..Ensure unlocked screen.. :/
Could it be an issue with the differen SDKS?
During a repair of all the SDKs, I found an issue with the event log, which I cleared based on The Event Log File is full
Still no success.
Extra
I cannot spin up the emulator from VS2013, when using the WP8.1 solution, but the wp8.0 solution in the same VS works :S
I found an error in a log file, from:
The errors are:
[0F08:14A8][2015-07-23T09:11:44]: Applying execute package: silverlight5_DRT, action: Repair, path: C:\ProgramData\Package Cache\DEB5078B60B74431E2830831EB48DF129CB32932\packages\Silverlight\5.0_DRT\Silverlight_Developer.exe, arguments: '"C:\ProgramData\Package Cache\DEB5078B60B74431E2830831EB48DF129CB32932\packages\Silverlight\5.0_DRT\Silverlight_Developer.exe" /q /ignorewarnings'
[0F08:14A8][2015-07-23T09:11:45]: Error 0x800705de: Process returned error: 0x5de
[0F08:14A8][2015-07-23T09:11:45]: Error 0x800705de: Failed to execute EXE package.
[0550:0E74][2015-07-23T09:11:45]: Error 0x800705de: Failed to configure per-machine EXE package.
[0550:0E74][2015-07-23T09:11:45]: MUX: Installation size in bytes for package: silverlight5_DRT MaxAppDrive: 0 MaxSysDrive: 0 AppDrive: 0 SysDrive: 0
AND
[0F08:14A8][2015-07-23T09:16:16]: Applying execute package:
{312d9252-c71c-4c84-b171-f4ad46e22098}, action: Repair, path:
C:\ProgramData\Package
Cache{312d9252-c71c-4c84-b171-f4ad46e22098}\VS2012.4.exe, arguments:
'"C:\ProgramData\Package
Cache{312d9252-c71c-4c84-b171-f4ad46e22098}\VS2012.4.exe" -repair
-quiet -burn.related.patch' [0F08:14A8][2015-07-23T09:16:23]: Error 0x80048bc7: Process returned error: 0x80048bc7
[0F08:14A8][2015-07-23T09:16:23]: Error 0x80048bc7: Failed to execute
EXE package. [0550:0E74][2015-07-23T09:16:23]: Error 0x80048bc7:
Failed to configure per-machine EXE package.
Anybody knows what to do with this? The error is coming when I repair Windows Phone SDK 8.0

There was a post-VS2013 update for the Windows Phone 8.1 SDK, some odds that you don't have it installed since you did not need it before. The download location is here.
Getting error messages like "port is in use" when there's no obvious reason why it should be in use and seeing excessive download times is also a very strong selector for your installed anti-malware product getting in the way. No specific advice on how to configure it when we don't know what it might be. You definitely first want to try to temporarily disable it so you can identify it as the source of the problem.

I have no Idea of what is the issue, but creating a new solution and importing the existing projects into a new solution has solved all the issues regarding emulator and debugger an AgHost.
Seems like the upgrade function integrated in the solution did not work properly.

Windows Phone Emulator Won't Start, NetBT error

Windows Phone Emulator can not start. When I try to start emulator say "Windows Phone Os is Starting". I looked the Computer Management/Event Viewer. When I try to start Windows phone Emulator, in the system log some errors appear.
1st
Log Name: System
Source: NetBT
Date: 12/8/2013 23:08:11
Event ID: 4307
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: birfincankafein
Description: Initialization failed because the transport refused to open initial addresses.
2nd:
Log Name: System
Source: Microsoft-Windows-Hyper-V-VmSwitch
Date: 12/8/2013 23:08:04
Event ID: 27
Task Category: (1019)
Level: Warning
Keywords:
User: SYSTEM
Computer: birfincankafein
Description:
Networking driver in Emulator 8.0.10322 WXGA.metehan loaded but has a different version from the server. Server version 5.0 Client version 4.0 (Virtual machine ID B0F3F3F5-7D6F-4551-848D-230DF063B1DF). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
3th:
Log Name: System
Source: storvsp
Date: 12/8/2013 23:08:01
Event ID: 6
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: birfincankafein
Description:
A storage device in 'Emulator 8.0.10322 WXGA.metehan' loaded but has a different version from the server. Server version 6.0 Client version 5.1 (Virtual machine ID B0F3F3F5-7D6F-4551-848D-230DF063B1DF). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Have you tried what it suggests in the error message?
To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
[edit]
I jumped ahead and tried this, but I don't think it will ultimately help you. I could insert the virtual Integration Services Setup Disk, but could not get it to run. See below...
Instead, I think you'll have to look wider to resolve this problem. First off, make sure you're running a host OS that supports Hyper-V, the virtual machine management component. This is the professional edition of Win7 (for VS2012) or Win8 (VS2013). If you do have a capable host OS, then try re-installing the existing instance of Visual Studio (Control, Programs and Features, right click on VS...). And if that doesn't work, remove Visual Studio, reboot, reinstall. And if that doesn't work, I know not what.
Here's what I tried with Integration Services. Maybe a wiser head can jump in and provide the missing magic...
on a Pro edition of Windows...
Install Hyper-V Manager, if you don't already have it. (Control
Panel, Programs and Features, Turn Windows Features On or Off,
select 'Hyper-V' then check both platform and management tools.).
Reboot.
Open Hyper-V manager(Home screen, start typing 'hyper', Search will
find it.)
Under 'Virtual Machines', highlight one of the Emulator ... virtual
machines. Right click, 'Connect'.
Verify emulator is currently powered off (i.e, not showing WP home
screen in emulator).
In 'Emulator ...' window, 'File' menu, choose 'Settings'.
In 'Settings for Emulator ...' window, highlight IDE controller 1'
in left hand panel.
In right hand panel, highlight 'DVD drive' and click Add.
Now start up the emulator VM. Back in 'Emulator ...' window,
'Action' menu, select 'Power on'. In the main panel, you should
shortly see the WP home screen.
Finally, 'Action' menu, 'Insert Integration Services Setup Disk'.
Hyper-V knows where it is.
And... nothing happens. I see no indication that the VM ran the setup program or did anything. Maybe, if your VM was somehow misconfigured in the first place, this will silently fix your problem. Friendly wizards invited to incant.

My service failed to uninstall

I recently tried to change the display name of my windows service, but apparantly I messed up. An old version fails to uninstall completely and I cannot install a new version of the windows service. This is the error generated from running installutil /i myService:
An exception occurred during the uninstallation of the System.Diagnostics.EventLogInstaller installer.
System.InvalidOperationException: The event log source '7 Ac Service' cannot be deleted, because it's equal to the log name.
An exception occurred while uninstalling. This exception will be ignored and the uninstall will continue. However, the application might not be fully uninstalled after the uninstall is complete.
So the event log source is equal to the log name. What does that mean and how do I fix it?

I found out myself. This post helped. So there are basically 3 places in the registry in the same name as the windows service. So I tried first to write a console application to remove the eventlog:
System.Diagnostics.EventLog.Delete("7 Ac Service");
It took care of 2 of them. I removed the last one manually using regedit. Then my windows service installed without problems.