Windows 8 store runtime error - windows-store-apps

I just installed windows 8 from the microsoft action pack (we have subscription for that).
After installing it, everything works as espected, but when I want to open the store I get an error message.
(I didn't install any software yet, so I don't understand why I get this error, my laptop is running in a domain)
runtime error
wwahost.exe
r6034
an application has made an attempt to load the C library incorrectly
please contact the application's support team for more information.

Related

HP Universal Printing Driver (UPD) 7.0

I have downloaded the most recent UPD PCL6 driver from HP home page. Its version 7.0.
We are using a solution call HP Access Control (16.8.1) which is a so called pull print solution.
I created a queue on my Windows Server 2016 and created a port. The HP Access Control comes along with its own port monitor.
I assigned the port to the queue and when I open the printer properties I get an error:
Function address 0x00007FFEB9E06402 caused a protection fault. (exception code 0xc0000005)
I have done this installation some time ago with the same version of HP Access Control and there all worked. Unfortunately I deleted that VM. But I believe I had an older version of UPD installed. Server operating system was also WS 2016.
I had posted the same question in the HP forum and got an answer.
For those who are interested:
**
The current UPD driver seems to have an issue if you assign it to
ports like LPT1 or File or 3rd party port monitors like those from
pull print solutions.
There seems to be a simple workaround:
If you can access a printer that is in your network, then you can
create a direct TCP/IP port and assign it to the queue you are having
problems with.
Then you can open properties or any other menu you get this error and
then make the changes you would like to do.
You can then re-assign the queue to the port which caused the error.
Alternatively, if you still have an older UPD version and that still
is fine for you then you can install the older version.
You should keep in mind though that the older version may not support
brand new printer models from HP.
But if you have not the latest freshly released models you should be
fine.
**

Runtime Exception in windows build

I am able to generate & install windows phone build in my Microsoft Lumia 640. Its running on Windows OS 8.1.
But as soon as I run application generated by CN1 build server, it gives error
An internal application error occurred: java.lang.RuntimeException Unsupported operation as per below screen shot.
For a testing purpose I created new CN1 Project and without changing any code / theme.res I just sent windows phone build and it ended up with the same error.
Unfortunately I didnt get any log output from windows phone, as it doesnt support Logcat like Android. Also I tried to grab Isolated Storage by WP Power Tools but there was nothing in it.
Anyone faced / facing this in Codename One windows phone build ?
The Windows Phone port is the least mature of the Codename One ports having gone thru 3 rewrites due to changes from Microsoft.
We are now debating the 4th rewrite, in the meantime some community members did their own port which should be more complete:
https://github.com/Pmovil/CN1WindowsPort
So as the short answer I suggest using that. For an explanation on how we got here read on.
The reason we didn't already start with the 4th port was Microsofts project astoria that they suddenly (might have) canceled. We were relying on this project for future Windows Phone support but now that its status is unclear we are in a bind.
We also have the JavaScript port & the Windows desktop port as options for targeting windows phone alleviating some of the problem.
If MS cancels the project for good we'll dedicate the resources for a complete rewrite of the port, but that will take time. However, we don't want to start off on such a huge effort and suddenly be faced with a huge shortcut of Android compatibility.

'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine' without need to install Access Engine

I've written an app which uses OLE DB, and I've encountered the error from the title. I've installed the Access Database Engine as suggested in this question and all had become work well. However, I want to distribute the app among some users to their locale machines and I have been reported such a error from the testers which do not have this util installed.
Is there any way to embed the Access Database Engine into my binary as dll or, maybe, into installer? I do not want to say "to use my app, install that util please"
if your end-user computer does not have MS office or MS Access installed, you won't be able to use the ACE.OLEDB driver UNLESS you install the basic access runtime/databse engine. However, if your end-users have 64bit windows and 32bit office, you will get the same error. To over come this issue you need to change your app target platform to x86.
if you are using visual studio, on additional way would be to add "AccessDatabaseEngine.exe" as one of your prerequisite which will be then installed along with your software.
more about custom bootstrapper:
http://msdn.microsoft.com/en-us/library/ms165429.aspx

Connecting Old ASP site to Access (.mdb) on server 2012

I feel that the title pretty much speaks for itself. I keep getting a server 500 error when i try to access a page on my site that is using the Access DB.
I created an ODBC (32 bit) Data Source using the driver Driver do Microsoft Access (*.mdb).
I am sure i am using the wrong drivers/IIS configurations. This used to be hosted on an old server and we are trying to move everything over.
Would anyone be able to point me in the right direction? Thanks!
EDIT
I was able to get errors printed to my page. Below is the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found
and no default driver specified
When I enable 32-bit Applications I get the following error:
HTTP Error 404.17 - Not Found
The requested content appears to be script and will
not be served by the static file handler.
This issue is related to running 32bit applications on a 64bit server. Furthermore, if you have installed something else on it (for example, Outlook Web Access, or OWA for short) it can disrupt the IIS with adding it's 64bit modules to load globally, and that would effectively cause errors on 32bit pools.
The following debugging is assuming you have a requirement to run 32bit ASP application on a 64bit IIS server.
You have to set your application pool to run as 32bit
If the 32bit pool stops right after you make a request for an ASP page, it means that most probably there are 64bit modules failing to load. You need to see which dll is creating the issues by viewing the Windows Event log (eventvwr). Then, one by one, you edit the applicationHost.config file and add preCondition="bitness64" to each module that you see in the eventvwr until you get rid of all the errors in the log.
When finished with step #2, your pool should be working, but your app might not - it will most probably report 404.17, even if there is an ISAPI handler for ASP. When you open IIS, on the left side choose the server and on the right open the ISAPI and CGI restrictions. You will see that there's an ASP entry there (if not - you need to install it as a feature on the server). The ASP might point to something like %windir%\system32\asp.dll, but you need to make another entry. Your appPool is running as 32bit on a 64bit machine (that's shortened as WOW64 = 32bit Windows application running on Windows 64bit - Windows on Windows64), and you need to add an asp from %windir%\SYSWOW64\asp.dll. Also, add the corresponding handler (navigate to handlers, and practically repeat the entry for asp but use the SYSWOW64 folder instead of system32)
This should (finally) get it working.

error running windows certification toolkit version 2.2

I recently updated the windows certification toolkit to version 2.2 and ever since the update I have been unable to run the toolkit against any of my windows store applications.
When I create packages within visual studio and run the toolkit as part of the wizard I get the following error:
the {0} cannot continue testing since the specified windows store app was not found. Please verify that the packagefullname is correct.
When I run the toolkit as a stand-alone application, I select 'windows store app' and it never finds any of my applications.
Anyone have ideas or suggestions that will help me from pulling out the rest of my hair?