I'm trying to deploy windows phone application to device and every time i'm getting the following error:
Error 16 Connection to device failed. For connecting to Windows Phone
8 device - Windows Phone IP over USB Transport (IpOverUsbSvc) is not
running. Retry after starting Windows Phone IP over USB Transport
(IpOverUsbSvc) from the services management console. For Windows Phone
7 device - Zune software is not launched. Retry after making sure that
Zune software is launched. 0 0
I went to the services console and discovered that IpOverUsbSvc is down. Unfortunately I failed to restart it with the following error:
https://www.dropbox.com/s/dp7hv9crhdoz6t3/IpOverUsbSvc_Error.png
When I went to the event log I found the following:
Application: IpOverUsbSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0FE7BEED
Faulting application name: IpOverUsbSvc.exe, version: 8.0.9903.0, time stamp: 0x505d196a
Faulting module name: IpOverUsbPc.DLL, version: 0.0.0.0, time stamp: 0x505d1a08
Exception code: 0xc0000005
Fault offset: 0x0001beed
Faulting process id: 0x18fc
Faulting application start time: 0x01cf11eacc0716b2
Faulting application path: C:\Program Files (x86)\Common Files\Microsoft Shared\Phone Tools\CoreCon\11.0\Bin\IpOverUsbSvc.exe
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Phone Tools\CoreCon\11.0\Bin\IpOverUsbPc.DLL
Report Id: 3135e02f-7dde-11e3-bec2-88532e5eb25c
Faulting package full name:
Faulting package-relative application ID:
Then I disconnected my phone and was able to restart the service. It was up and running. Unfortunately when I connected my phone again service was terminated right away with the same errors (above).
Please advise.
I had the same problem some time back.. Can you pls try uninstalling your device driver and installing it again. This may resolve your error..
I come here to bring solution that u might like
I suggest you to try open service menu on your OS Windows here's the screnshot
on the form try to search Windows phone IP over USB Transport (IpOverUsbSvc)then u should right click and Start it
then you may deploy your apps and see whether this solution works or no.
Related
My System (Windows 8 running in VirtualBox) shutdowned unexpectedly. When I restarted the system Veracypt wouldn't start saying. "The device is not ready. Source: Mounted:4743"
Restarting the system seem to have solved the problem
A Simple KDMF USB Driver is deployed on a target machine
Target Machine has a USB Sniffer installed
Target is Win 8.1 (x64)
Host is Win 2012 Ent (x64)
WinDbg Remote Debugging Toolset is used
Target is provisioned
Breakpoints are set using the Visual Studio
IDE Deployment succeed, no errors at setupapi.dev.log
The USB Sniffer shows the URB interaction triggered by the deployed KMDF USB Driver Indicating the driver is actually running.
Although the driver is running and the debugger seemed to be attached execution doesn't break at any of the breakpoints set.
The debugger doesn't automatically break once attached.
Manually Breaking execution and running "x *!" verify that the KDMF USB Driver is loaded.
Manually Breaking execution and running "x %Driver Name%!*" verify that the
KDMF USB Driver symbols are properly loaded.
Manually Breaking execution and running "bl" list no breakpoints
Having the above in mind, why does the debugger doesn't break execution at the pre-defined break-points? why does the WinDbg "bl" command list no break points although few are set using the Visual Studio IDE?
Re-provisioning/rebooting/... doesn't resolve the problem
Any help will be appreciated
Update
I have cleaned any residuals of the driver from the system ( including driver cache cleanup using pnputil.exe -d )
Only then, setupapi.dev.log say the following:
Verifying file against specific (valid) catalog failed! (0x800b0109)
{_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 09:09:16.117
...
Success: File is signed in Authenticode(tm) catalog.
{_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 09:09:16.137
...
The driver IS SIGNED with a valid verisign certificate, is there any specific req for that certificate?
Should this cause the problem I am experiencing?
I have to maintain a WDF driver. This is a no-hardware driver: the driver use a disk file which is mounted as a Windows partition. All the data written to the disk are encrypted by the driver. The driver run in kernel mode.
The driver has been developed on XP and successfully ported on Vista and 7, 32 & 64 bits. I encounter one big problem on Windows 8. The driver lead to a fatal system error:
BugCheck 50, {ffffffffffffffd0, 0, fffff800002de33a, 0}
Probably caused by : Wdf01000.sys ( Wdf01000!FxDevice::DispatchWithLock+fa )
The problem occurs after deleting the device with WdfObjectDelete(). As long as the device is not deleted the driver run fine and there is no system error. When WdfObjectDelete has been called, the system crashes after a certain delay.
verifier detects no error in the driver. My questions are the following:
Is there anything special regarding WDF on Windows 8?
Is there any tool/technique that could help me finding the bug in the driver?
There shouldn't be anything specific to Windows 8 for this issue. I'd recommend starting to debug your driver with WinDbg via a remote system. With this you can set breakpoints, step through the code and most importantly get post-mortem information on the crash. Once you have connected a machine, and you can see they crash use analyze -v to get information. OSR is a great resource for BSOD debugging.
The system configuration I am using is as following:
OS - Windows 7 (64 bit)
RAM - 8GB
Eclipse - Kepler release
Java - 1.6.0_45 (64 bit)
Android SDK - 22.2.1
ADT - 22.2.1.v201309180102-833290
Graphics Card - Intel(R) HD Graphics 400, version - 8.15.10.2696
When I create a new AVD and launch it an error always comes up - 'emulator-arm.exe has stopped working' - with the following details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: emulator-arm.exe
Application Version: 0.0.0.0
Application Timestamp: 5238f89b
Fault Module Name: ig7icd32.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f67b1c8
Exception Code: c0000005
Exception Offset: 000256e6
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I have gone through various other questions addressing this issue as following:
emulator.exe has stop working?
Error Message: emulator-arm.exe has stopped working
emulator-arm.exe has stopped working
I have tried all the following options suggested by them:
Change the RAM value - I have tried with all values ranging from 256 to 1907
Change the target - Have tried the versions from 4.1.2, 4.2.2, 4.2 along with their Google APIs
Change the device - Have tried with various versions of Nexus along with WSVGA
Change the Heap - Have tried with different values of Heap size
Change the resolution - Have tried with various resolutions as per the device
But every time, for every new AVD, as soon as I launch it, I am getting the same error - 'emulator-arm.exe has stopped working' - with exactly the same Problem Signature as shared above.
Could someone point me in the right direction that how can this be resolved?
UPDATE: I invoked Android Debug Monitor to view the LogCat when the device is being launched but there are no log messages getting displayed there.
Any suggestions anyone on how to resolve this?
Try turning off the "Use host GPU" option. Perhaps your computer's GPU is not compatible with the emulator.
This may be due to a compatibility problem with the Intel HD Graphics driver. I would suggest you to update the driver to the latest available version and check.
The crash details point to ntdll.dll
When I searched on the internet, I see a lot of application problems reported in Windows 20008 Server because of this dll.
My Windows Server 2008 machine is updated with latest packs and updates.
Is this is OS problem or my application which is buggy?
Problem signature:
Problem Event Name: APPCRASH
Application Name: Client.exe
Application Version: 1.3.0.0
Application Timestamp: 51cbcdde
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6002.18541
Fault Module Timestamp: 4ec3e3d5
Exception Code: c0000005
Exception Offset: 000665c9
OS Version: 6.0.6002.2.2.0.274.10
Locale ID: 1033
Additional Information 1: ccc2
Additional Information 2: 0a07f28ebf2977f2668fa7213522081c
Additional Information 3: 1ac0
Additional Information 4: 79391a57c1698c1550ee327c075e511e