I wrote a windows service (Win32 API) that uses a .NET assembly written in C#.
The service is set up to start automatically. In Windows XP all works well but under Vista the service is not automatically started (after reboot) because the .NET component is throwing an exception. But if I start the service manually, it works well.
It seems to be a security problem. The service is running under the local system account.
Related
I'm working with a legacy c# console application that uses WCF and MSMQ. It's several years old and was developed under VS2015 running in Windows 7. It runs fine in that environment.
But, when I simply copy the project to a Windows 10 machine running VS2019 and run the application in the VS2019 debugger I get the following exception when it attempts to queue a WCF/MSMQ message...
An error occurred while opening the queue:The queue does not exist or you do not have sufficient permissions to perform the operation. (-1072824317, 0xc00e0003). The message cannot be sent or received from the queue. Ensure that MSMQ is installed and running. Also ensure that the queue is available to open with the required access mode and authorization.
The queue does exist. In fact the app actually creates it if it's not there - which it did on 1st run.
Under Message Queuing the associated queue has full access granted to my user account.
MSMQ is installed. Again, the app itself created a queue.
I'm running VS2019 (and therefore the application under debug) "as an administrator" - which is another pain...
Again, this runs just fine in the older Windows 7 / VS2015 environment. It's only when the project is copied into the Windows 10 / VS2019 environment. Obviously there's some setting in the new environment...
Any thoughts?
Many thanks!
-- Curt
This may be due to a problem with the base address in the configuration file. The server name needs to be included in the base address. If the server name of win7 and the server name of win10 are different, it may cause this problem. There are similar questions in this blog, you can refer to it.
For more information about "Message Queuing to Windows Communication Foundation", you can refer to this link:
https://learn.microsoft.com/en-us/dotnet/framework/wcf/samples/message-queuing-to-wcf
I have been building a windows application. this application contains a windows service which performs certain action when the service is started, for example some FileIO operation.
Now this application needs to be deployed on the server. The server, obviously won't have visual studio in it. So how can i install that windows service there along with the application.
NOTE :- application is installed, just need to know how can i install the windows service.
Thanks in advance.
I am trying to call the COM library method(COM interopablity) from ASMX webservice hosted in IIS 8.5 & Windows Server 2012 64 bit server. But the call doesnt respond. I have done the following changes to ensure we are doing the right setup
1. Enable 32 bit application = true for application pool setup
2. Registered the COM in the following locations
C:\Windows\System32 & C:\Windows\SysWoW64
3. Tried compile the webservice project to target X86 configuration
4. Changed the execution timeout for web service to 10 mins
5. Did setup application pool identity which worked for my windows application
But none of the above works.
Just to verify .Net and COM communication, I have created the windows
application to call the same method and it works when I compile the
project in X86 platform.
If I compile the windows application to target platform to Any CPU, I
get the same issue like calling it via ASMX web service. Its not
responding to the call.
Finaly, It looks like it is working for windows application target x86
platform. But no idea, why it is not working from asmx service when I
set Enable 32 bit application.
Could you help me to identify what could be the wrong with ASMX to COM call?
Referenced:
Error 80040154 (Class not registered exception) when initializing VCProjectEngineObject (Microsoft.VisualStudio.VCProjectEngine.dll)
How to repair COMException error 80040154?
Note: I was getting COM exception 80040154 error when COM was not installed on C:\Windows\System32 folder. Now not getting this error but call not responds.
Server is 64bit
Depending on the COM server you invoke, you may need to specify an Identity for an Application Pool if the COM application requires a user profile, or check the app pool's Load User Profile property. (I needed this to run ABCpdf, for example)
In my Windows 10 UWP app I am using a MapControl and ApplicationInsights. I see reports of crashes of that app, which I cannot reproduce or know how to fix. The only information the crash reports are offering is the following:
A privilege that the service requires to function properly does not
exist in the service account configuration. You may use the Services
Microsoft Management Console (MMC) snap-in (services.msc) and the
Local Security Settings MMC snap-in (secpol.msc) to view the service
configuration and the account configuration. The internal MapControl
framework failed to initialize.
Seems like the crash occurs at the app start, as I appears even before the "MainPageView"-eventreport of Application Insights. Is anyone in the same situation or knows a fix for this issue?
Had the exact same issue with a Lumia 925 updated to Windows 10 Mobile, and in the end it seemed that the entire Maps framework was corrupt on that specific device.
You can check that the problem happens to any application that uses a MapControl by opening the native Maps application - if it crashes too, you will have to wipe and reinstall Windows 10 Mobile on that device.
Production Server: Windows Server 2008 R2 Enterprise Edition
Development Server: Windows Server 2008 R2 Standard
I wanted to start an .exe at the system startup. I have created a windows service using .Net, which starts the exe on service start.
In Developmenet deployed the service and it is working fine.
Service Name: ExeStart
Display Name: ExeStart
Logon using – Local System Account
Startup Type: Automatic(Delay Start)
Deployed the same service to UAT server, where the service is showing running but not working as expected. In the task manager I can see that exe is running.
If the exe started manually, it is showing 7MB memory in task manager, while started from the service it is only showing 4MB memory.
Is there any dependencies failed while starting the service?? If so, how could I find out dependencies of this service.
This service is running, exe is showing running but not working. What could be the issue here?