I'm using media foundation player for rendering video in my app window.
On my host machine everything is ok, but when i run my app automaticaly (on the remote build server), MFPCreateMediaPlayer call returns with 0x80040154 error code ("Class not registered").
How it is possible to register class, how can i figure, which class needs to be registered, why this issue appears only on the remotes? Any usefull links are acceptable.
Tnx!
ANSWER: i find out, that problem was caused by disabled Desktop Experience service. As i enable this service and restart build server (running on Windows Server 2008 R2), MFPCreateMediaPlayer call return success code and video starts to play. Hope it can helps someone.
ANSWER: i found out, that problem was caused by disabled Desktop Experience service. As i enable this service and restart build server (running on Windows Server 2008 R2), MFPCreateMediaPlayer call return success code and video starts to play. Hope it can helps someone.
Related
I'm having a very strange problem with an application in windows 10. It consists of several .exe in the same computer communicating between them with sockets using system.net.sockets library.
The problem I have is that after installing Windows 10 in a new computer, install all windows updates and then installing that application, connection to sockets doesn't work correctly and the application fails. The strangest thing is that if you leave the computer alone for 1-2 days the applications starts working just fine. The same has happened after installing version 1803 update, it stops working and then works one or two days later.
Any idea of what can it be? Has anyone seen something similar?
It really seems to be related to the 1803 update you mentioned.
Symptoms:
Running an application from a network share will fail when creating a socket;
Copying the very same application to a local drive/path will work just fine, without any further modification.
We are also struggling with this while connecting to an Oracle database (both ODBC and ODP.NET) and it seems the issue has recently been acknowledged:
https://support.oracle.com/knowledge/Oracle%20Database%20Products/2399465_1.html
It also seems this is a recurrent Windows bug:
Win Socket Creation fails with Error code 10022 if non super user
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/3076a9cd-57a0-418d-8de1-07adc3b486bb/socket-fails-with-error-10022-when-application-is-run-from-certain-network-shares-on-vista-and?forum=wsk
Sorry, no effective solution at the time (other than copying the app binaries to a local folder). I'll update this answer once we get a better solution.
OK, looking a little further I found here in SO that this might be related to a SMBv1 network share, which describes the environment we had here (the network share was disabled because of another bug we faced - thanks MSFT).
Re-enabling SMBv2 / SMBv3 on the server solved the issue.
Related post:
After Windows 10 update 1803 my program can't open a socket when running from network share
I um using Windows Azure toolkit for Windows Phone from codeplex. After creating a Windows Phone Cloud Application from a template, I started it on localhost and it run succesfully. Then i followed instructions on Codeplex on how to deploy on Azure, and published it also succesfully - I got an url to the website, but after typing the url in browser the website didn't load, and after a while there was a timeout. I tried both production and staging deployment. Can't resolve why this happens - did anyone faced familiar problem?
The publish completed successfully however this application is not running properly on Windows Azure.
As you are using Web Role type WP7 Phone application look for all the steps suggested in the link below:
Webrole is not starting and always busy
Also if you still could not find the root cause open a Windows Azure support ticket and you will get some help to find the root cause.
You may want to look at:
http://msdn.microsoft.com/en-us/library/windowsazure/hh134844.aspx
Remoting into the VM is a great way to see what is going on. Does it come up if you want for a while (maybe 30 minutes)?
I have two cloud solutions (.ccproj files). Each has a single distinct web role. One project runs under Compute Emulator without any problems but when I try to run another one (the first one not running) Visual Studio will package it and then display
Windows Azure Tools: There was no endpoint listening at net.pipe://localhost/dfagent/2/host that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Windows Azure Tools: The Windows Azure compute emulator is not running or responding. Stopping the debugging session.
I'm using SDK version 1.4
I Googled for a while but couldn't find anything that could help me. Force starting the Compute Emulator (csrun /devfabric:start) doesn't seem to help.
How do I resolve this problem?
Although an old question, I got this issue recently and the reason for it was that - while the service or website in azure would have been removed or stopped and you try to publish to it. If this happens, check the publish profile to see that you are pointing to the correct service/site including the storage acc etc and correct them. Hope it helps someone.
I have a strange issue. Have a windows service running on Windows Server 2008 that receives files over TCP and saves to disk. Initially service was running as Local System account. It worked ok for 7 days and stopped receiving. From the sender side connection succeeds but send fails. The service blocks forever on receive and connection times out.
I changed the user account to "Network Service" and it started working again for 7 days and stopped. I then changed it to run as administrator. It ran for 4 days and stopped again. Now whatever I try it does not work. Rebuilt the code re-installed the service but same issue.
Does anybody ever face such an issue? is it a virus or something? Is windows blocking it? any suggestions will be greatly appreciated.
Note: If I run it as a windows form application it just works fine. Also disabled the firewall but it did not help. While debugging the code I never see any issues. Because it works as a forms app and also worked perfectly as a service for 15-20 days now.
I figured out the problem. When the issue started happening I ran the Filemon utility and figured that the service was failing to access a temp file created using GetTempFileName().
This seems to be a known issue with Windows server 2008R2 and happens randomly.
Here is a solution/Hotfix from Microsoft: http://support.microsoft.com/kb/982613
We have a WCF service that generates an Excel file off of a template and feeds it back to the client in a byte array. For some reason, we are getting an error when we try to do this:
sheet.PageSetup.CenterHeader = sheet.PageSetup.CenterHeader.Replace("[customerName]", customerName).Replace("[dateTime]", date.ToShortDateString());
When it hits this line, we get this error message:
No printers are installed. To install a printer:
In Microsoft Windows 2000, click Start, point to Settings, and then click Printers. Double-click Add Printer.
In Microsoft Windows XP, click Start, and then click Printers and Faxes. Under Printer Tasks, click Add a printer.
Follow the instructions in the wizard.
The service runs under the LocalSystem account. When we first deployed this service, it was to an x64 machine and had the same issue. Our dev environment is x86 so we moved the service to another server that was x86 and it worked fine for a while. It recently stopped working and is now giving us this error message again. I am pretty sure it was becuase of a mass windows update that was done on the app server recently.
Funny thing is, I tried changing the service to "allow interaction with the desktop" and it didn't work, but when our sysadmin did that same thing, it worked for one file generation but is not working now.
There are printers installed on the machine, both on domain accounts and local accounts. I've also tried running the service under a different account, but then I wasn't able to connect to the service due to some SSPI error. We tried using the Network Service account but then the app couldn't see the service at all. We've restarted the service after each change also to no avail.
What I do know about the "PageSetup" part of the sheet object is that it needs to have a printer installed to access it at all, even if you aren't printing. I was unable to figure out a way to trick the machine into thinking the LocalSystem account has a printer installed.
We figured out the problem, I had my config file still pointed at the x64 server :(
As to why it won't work on x64 (to my knowledge) - since office 2003 is x86, it needs an x86 print spooler in order to work correctly. I don't know of any way to get an x86 print spooler on an x64 OS so we just stuck it on the x86 server.