This is problem with deleting a printer driver in windows 8 pc.
Our applicaton is working fine in UI Level deployment, we have installed and uninstalled successfully.
we have tested our Application in Windows 8 (32 and 64 bit) from UI Level and as well as PUSH Deployments.
But in PUSH (Active Directory deployment), "OpenPrinter()" function is failed to get the handle of requested printer driver. Then the deleteprinter also failed.
We have verified that the function is getting perameters as we expected. But it is failed.
Since the issue is happening only in Windows 8.
Servers are Windows 2003 and Windows 2008 r2 and Deploying per mechine basis.
Application developed in VC++ (VS 2008) and packaged with InstallShield12.
In our investigation we have found that Registry is not accessible to 'Openprinter()' function and it is failed to return the handle.
While we install the applicaton from PUSH, it is installing with SYSTEM account. We have verified this.
Is there any limitations to use the registry in Windows 8 PC?
or do we need to fix/set/configure any settings in Windows 8 PC?
or Is there any forbidden to access the registry for SYSTEM account?
Please help me to resolve the issue.
Thanks in advance.
Registry is not accessible in Windows 8 (32/64 bit) while active directory deploymentFinally things are broken out..The main reason is openprinter API depends on registry to get the handle for requested printer.By the time we have called the API, the registry is not available for it. when we have waited to complete 2 minutes, the API returns the handle.hence my PUSH uninstall is completed with out hang. Now problem is solved in my case.But it is a limitation with Windows 8.
Related
This is regarding Abbyy Setup issue that we are facing on a Azure Cloud Machine which is a Windows Server 2019 VM.
We followed the Admin Guide for Reader 12, the "Manual Runtime Installation Steps" were followed for the setup. The Bin64, Data and Inc folders are copied into a directory which will be later used while registering FREngine.dll on the OS. We have not done the Abbyy SDK installation.
We have VM setup locally which is a Windows Server 2019 VM image. On this setup we are able to Register the FREngine.dll successfully using regsvr32 command. Also we don’t see any issue and is working, w.r.t reading OCR/Barcode values successfully through Abbyy FineReader.
ISSUE
The issue is on the Azure Cloud System [VM Windows Server 2019], where we are able to Register the FREngine.dll successfully using regsvr32 command. However even with the successful Registration of FREngine.dll, when we try to initialize the FREngine, we are getting an exception "Invalid Engine instance" during the call to InitializeEngine( ) with all the Required parameters set.
// Create the abbyy engine instance in outproc process,
// as its recommended by Abbyy for 64-bit process
outProcLoader = new OutprocLoader();
if (outProcLoader != null)
engine = outProcLoader.InitializeEngine(AbbyyEngineUtils._strProjectId,
engLicensePath,
AbbyyEngineUtils._strEngPwd,
"", "", true);
Here we have a license file which is also copied into the location where FREngine.dll is present.
Due to this initial Step failure Abbyy Logs could not be generated from the codebase. However we see a log file that gets generated from Abbyy in the path “C:\ProgramData\ABBYY\SDK\12\FineReader Engine\” at this point of failure which states as follows:
10552 :ABBYY Licensing Service is unavailable: The RPC server is
unavailable.
We also we additionally tried running the Abbyy SDK’s Sample applications on this machine. This also fails with the above error during Abbyy Engine Initialization.
How can this be resolved?
More Info on Licensing Service:
We additionally tried installing the LicensingService and the LicensingSettings.XML had :
ProtocolType="LocalInterprocessCommunication" />
Here Ours is a Standalone Abbyy Installation and hence the Protocol Type used is LocalInterprocessCommunication which is for the local Licensing Service. It is not necessary to specify this protocol type for Standalone installation, as Standalone licenses are always used with the LocalInterprocessCommunication protocol type.
This was an additional Step tried by us. However the actual issue was with the Abbyy Licensing on Azure.
Did you happen to start the abbyy licensing service in the Azure VM ?
(Windows Key + R) Run command --> services.msc
In the Services Dialog, find the Abby...Licensing service.
Right Click -> Properties
You can click on the start and click ok.
Retry your above steps. Also, you could have startup type as Automatic if this works in the services in dialog.
As any other OCR solution some have licensing constraint to run on Azure and AWS , make sure your license is compatible.
as posted here
https://support.abbyy.com/hc/en-us/articles/360016441600-Can-I-run-FineReader-Engine-in-Virtual-Machine-or-Container-
also I would check the OS compatible version.
ABBYY SDK 12 Licensing Service has been tested in the following virtual environments:
Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2
Windows 10, Windows 8.1, Windows 8, Windows 7 SP1
Hi I am trying out Microsoft Azure Remote App Services.It asks me to download a client to connect to remote app server to run the apps on my local machine. I downloaded the cleint (rdClickOnceLauncher.application), but this doesn't launch and asks for an associated program to open with. I am not sure how to open such programs. Could any one guide me?
OS:Windows 7 Professional Service Pack 1
Thanks
I nailed it. It open with "C:\WINDOWS\system32\dfshim.dll" for 32 bit systems and C:\windows\sysWOW64\dfshim.dll for 64 bit systems clickonce application deployment support library.
I have universal project targeting Windows Store 8.1 and Windows Phone 8.1 platform.
The windows one works fine but I having trouble running the WP one on an emulator. I get the error message saying:
Microsoft Visual Studio Unable to activate Windows Store app
'numbers-here!App'. The Kiss.WindowsPhone.exe process started, but the
activation request failed with error 'Msg in polish that the app did
not start'.
If this was Windows I would check System Event Log and see the logs just before the error what DLL the system was trying to load and that helped a lot when I was debugging similar problem with Windows Store project, here I have no clue on how to check what exactly was being loaded.
The worst part is that I created package (appx) and checked the dll's being packed with exe, it seems that it includes dependencies that the app explicility uses yet something is still missing and this might be some 'hidden' dependency of one of the other dlls.
Any ideas how to debug such issues with emulator?
For me it was due to having WIC code in my App and/or calling CoCreateInstance in a windows phone environment ( on PC it works flawlessly though )
I ran into the same problem on Windows 10. Turns out, that there is no Kernel32.dll on Windows 10 phone!
Instead you need to link against OneCore.lib which provides the entire Win32 API subset that is supported in UWP. This "umbrella library" will load the correct dlls at runtime.
See also:
https://msdn.microsoft.com/en-us/library/windows/desktop/mt683763(v=vs.85).aspx
I install my EF5 winforms application using Click Once.
When I installed on a Windows 7 virtual computer it worked correctly, however when I installed on a Windows XP virtual computer I got an "underlying provider failed on open" error.
I consulted this link and decided to look at the Distributed Transaction Coordinator in component services on the XP computer..
I only viewed things in component services, by expanding the tree.
Now my application works, and I don't understand why it didn't or why it is fixed.
Can anyone explain this to me?
I just upgraded my Azure solution to VS2012 and October 2012 version. I have 2 webroles but only 1 of them is working now when I look it from IIS Manager. I'm sure of it because my webrole's inter-role communication requests are failing too.
First I tought it can be another problem so I asked this question: Windows 8 Azure Emulator is Remapping Port 80 to 81
Here you can see my IIS Manager:
I had the same issue, and RESOLVED it following the suggested Registry hack here:
Strange behavior of Windows Azure Compute Emulator (SDK 1.8) with multiple role instances on a clean machine with VS2012 but WITHOUT VS2010
Anyone with this issue, please pile onto this connect log for MS to properly fix:
https://connect.microsoft.com/VisualStudio/feedback/details/773786/azure-sdk-1-8-binds-several-web-roles-to-the-same-port-on-local-emulator
It's a bug, I hope it's fixed in the next update by Microsoft. Definitely happens if you have VS2012 on Windows 8 and didn't install/upgrade VS2010
Workaround:
Create a text file (*.reg) with this and import into your registry (double click .reg file in explorer)
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing\10.0]
"SP"=dword:00000001
Kill the process i.e. exit VS2012, exit compute emulator (or just reboot if in doubt).
Fire it up again!