I am trying to debug my Windows Phone 7 app, and I am getting the following error upon launching the app in the emulator (via VS2010 debug):
Unable to start program
'\Windows\tashost.exe\'
The drive cannot locate a specific area or track.
Any ideas as what may be causing this? The most recent change I made was adding functionality to save game data, via the IsolatedStorageFile. However, it was working for a while with this functionality in there.
I found the problem. If only I had read the release notes. For anyone else that might be experiencing this issue, it is addressed in the WPDT Beta Release Notes.
Release Notes - WPDT Beta 7/16/2010
Unable to start program error if
project not configured to build or
deploy. If a project is not configured
to build and or deploy a game, the
operation will fail with the following
error message:
Unable to start program
'\Windows\taskhost.exe'.
The drive cannot locate a specific area or track
on the disk.
To set a game project to
build or deploy: In Visual Studio 2010
Express for Windows Phone, click
Tools, then click Settings, then click
Expert Settings to enable the Solution
Configurations drop-down. From the
Solution Configurations drop-down in
the standard toolbar, select
Configuration Manager. Check the Build
and Deploy checkboxes.
what worked for me was to update my graphic card driver. Even though my computer said the device was up to date, going to the manufacturer website and downloading the latest drive allowed it to work. (using Nvidia by the way) this was after after about 5 hours of trying to figure this thing out.
also make sure you all the rest of your updates are up to date, and that directX is current.
Related
I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.
I am new to Kony enterprise edition. I tried to run my app using the Android emulator, always its showing unknown error (code 100-ref img), when I click OK, its closing app, I check the Support x86 devices in the settings. I install the apk using cmd, app installed but when I tried to open the app is showing the kony animation with launching icons. I tried to used local host in the kony app but no use. I am unable to guess the what is the error, and what went wrond. Requesting great help to run the app, and kony editor is taking very long period to build in at least in one platform (like android, desktop etc). Its killing my time for building app rather than development. Appreciate any tips to build as fast as possible and track errors.
You can check the error's cause in DDMS(WINDOWS key+R -> DDMS -> press Enter). It should log the message for the cause of your error. Change the debug level to Error if there're too many messages.
As for making the build faster, it's mostly system-dependent, although you can make a few changes that might positively affect build times. Do this: go to your Kony studio's installation folder and find the eclipse.ini file. Open it and change the values of parameters like -Xmx and -XmsMaxPermSize to a higher number. e.g from -Xmx512m to -Xmx1024m. Now restart Kony studio. As an aside, a machine with a minimum of 8GB ram is recommended, with as less programs running as possible apart from Kony.
Lastly, and this is my opinion, Kony preview is basically a sub-optimal feature that's rarely used by any Kony dev I've ever met. You're better off running the final build on a device.
I'm trying to run blocs editor for app inventor. It's starting slowly and then returns message:
We could not download the starter application from the server in order to install it on the device. This may prevent the "Connect to Device" button from working.
This error can occur if you have tried to start the blocks editor with a previously downloaded ".jnlp" file.
I have installed last version of java, other java applications are working fine. How does make the block editor work?
There could be lots of reasons. Which browser are you using? Did you already try another?
Probably there is some kind blocking software running on your machine, perhaps a firewall. There have also been reports of this from misconfigured virus scanners.
You also might want to take a look at the troubleshooting page. If this does not help, post a question in the Getting Set Up and Connecting Your Phone to App Inventor forum.
I've built a Windows Phone application and was successfully able to get it into the store. I made a few improvements and created a Windows Phone 8 version and submitted the update. However, it keeps failing the certification process (3 times now). I found one issue with the Windows Phone 7.x version and was able to fix that, but now I'm just getting an error that my application fails to run with a silent failure.
I've tried everything I can think of in emulators and devices, but I can't seem to get the failure to happen. It would really be nice if Microsoft would give you more information. Since they don't, I was wondering if anyone had a good list of all the different condition, devices, and steps you go through to test your application before submitting it.
So what are the recommended testing scenarios to test an app in before submitting it to the store?
(What would be really nice would be to see what steps Microsoft uses when they test an app)
BTW - I should mention that I've used the certification tool and the simulation dashboard in my own testing.
Most of the tests used for WP7/WP8 certification are public and can be seen as part of the Windows Phone certification guidelines: App submission requirements for Windows Phone, Technical certification requirements for Windows Phone and Additional requirements for specific app types for Windows Phone. Have a look at the column titled "Test Steps".
Couple of thoughts regarding you specific issue:
Can you share you specific failure report NSTL test results pdf file?
A good way to make sure your second submission goes through is to simply fix the failure from the first submission, and under the "tester notes" say that it's the exact same XAP with one small fix and how it was fixed.
If you can't repro an issue encountered by the testers, you can always resubmit and under the "tester notes" saying just that and ask for more details if it fails again.
The test team may be using 256MB devices (Lumia 610) for WP7 testing and 512MB devices (Lumia 620) for WP8 testing. Have you tested your app in the emulator under those configurations?
We got this problem recently on our two apps on which the another one was an app we did only some text changes. The previous version passed and launced well and the new version did not.
Our reason was very similar as what Bryant tells.
What we did was that after our changes we run the 'Preemptive Solutions Dotfuscator For Marketplace Apps' and upload the dotfuscated xap-file. On our cases the Dotfuscator had changed the size of our own DLL-file (we have our own custom controls for buttons to have two title-lines on the button). At the moment I don't know reason to this but I feel that somehow the Dotfuscator does not found our own DLL properly while dotfuscating (this our DLL is on the References of our project)).
So one reason can be that something goes wrong while dotfuscating. For this reason one should test the dotfuscated xap-file by installing it onto the phone using 'Application Deployment Tool'.
The files and especially the DLL-files inside a yourapp.xap-file can be seen by renaming the file to yourapp.zip and then extracting it.
Tapani
I am using Google Desktop on my machine.
When I want to build my Silverlight 4 app in Visual studio 2010, 1 out of 30 (roughly) times the build will fail saying "The "SubsetFontsSilverlight" task failed unexpectedly" and then it explains that the process cannot access a file in ...\obj\Debug\Fonts\Fonts.zip because it is being used by another process.
By trial-and-error I found out that if I close Google Desktop the problem goes away (I assume google desktop is currently indexing the file). The only way to solve this problem and compile my app again is to completely shut down Google Desktop. This is annoying. Does anybody have a workaround for this?
Thanks.
Jan
If it's Google Desktop then you can exclude directories. See this link:
http://desktop.google.com/support/bin/answer.py?hl=en&answer=10117
Also, if it's not Google Desktop it could be an AntiVirus application that needs to exclude that directory.