Application that uses MSXML6 IServerXMLHTTPRequest.Open Fails when run on machines with OS WIndowsEmbeddedPOSready7 & windows7 Pro. Works fine on Windows 8 and Windows 10. I have installed MSXML 6 on all the machines. The application creates the object ok on all machines but the open fails on machines running OS
WindowsEmbeddedPOSready7 & Windows7 Pro
Turns out a URL of http://10.1.1.61:10009 is fine for windows 8, windows 10 but on windows 7 and POSReady7 and XP SP3 the open will fail.
If you add a / to the end the open worls on all OSs.
So http://10.1.1.61:10009/ solves all the problems. The cryptic result from the open of
lResult& = OBJRESULT returns -2147012891 does not tell you much. It was pointed out to me that if you search the web, but use the hexadecimal value for the search you can find out the error means Invalid URL?
Related
I am getting sqlite3.dll not found error at Autohotkey app. I already have sqlite3.dll file in the Project at sqlite3.dll
The error is produced here SQLite_L.ahk#L107 :
if(FileExist(sqliteDllPath)){
DLL := DllCall("LoadLibrary", "Str", sqliteDllPath)
if(!DLL)
throw Exception("Can't load " . sqliteDllPath . "! (token:18-10-12_11-52. BTW DllCall is in AHK v2 is case sensitive)", -1)
Within this application, i worked without problem at
64-Bit Windows 10 10.0 lenovo t540p (Admin-Account).
Also worked for others in the circle of friends (not Admin-Account).
A user reported my this error into the AHK-Forum.
My first Steps:
During my recherche i found:
[DllCall is in AHK v2 is case sensitive][3]
I guess he'll use the version 2.
So everywhere I changed SQLite3.dll to sqlite3.dll
But Today i got this error at another Laptop (fresh downloadet from github).
I have therefore unpacked the project in different directories.
[3]: https://autohotkey.com/boards/viewtopic.php?t=3280 "DllCall is in AHK v2 is case sensitive". No success.
the SQLite dll is 64-bit DLL (sha1: 9fad624c1aa1c0c9ba20230f2e176fac305edac5)
but installed was a 32-bit AHK
A_Is64bitOS [v1.1.08+]: Contains 1 (true) if the OS is 64-bit
A_PtrSize [v1.0.90+]: Contains the size of a pointer, in bytes. if the AHK is 64-bit 8.
If ahk is updated to 64 bit, this error message disappears.
Ideally, this should also be checked in the script.
ahkIs64version := (A_PtrSize=8 ? "64-bit" : "32-bit")
MsgBox % "Script is MsgBox % "Script is . (ahkIs64version ? "64-bit" : "32-bit")
if(!ahkIs64version)
MsgBox,% "Error: AHK Version (32-bit) not match to Sqlite Version (64 bit). Please update your ahk-Version or choose another Sqlite Version"
When I call a Java Stored Procedure in c-treeACE SQL Explorer, for example: call myProc(), an error happened:
Error : -20160 Error Description : Java SP/T Feature not supported.
My environment:
OS: Win 10 64bit
c-treeACE: V11.0.0 32bit
JDK/JRE: jdk1.6.0_31 64 bit, or jdk 1.8 64 bit, or jdk 1.6 32 bit
Also, I have already Setting in ctsrvr.cfg for Java Stored Procedure
Support(also restart the c-treeACE service):
SETENV CLASSPATH=D:\Work\Db\d3dxsapi\Java\jre6\lib\rt.jar;C:\FairCom\V11.0.0\win32\bin\ace\sql\classes\ctreeSQLSP.jar
SETENV JVM_LIB=D:\Work\Db\d3dxsapi\Java\jre6\bin\client\jvm.dll
SETENV JAVA_COMPILER=D:\Work\Db\d3dxsapi\Java\jdk1_6_0_31\bin\javac.exe
Any one know this, could you please help me? Thanks!
I used another jdk 1.6(32 bit) to figure it out.
I just update Xcode 7.2 to 7.3. My app fetch and store files on icloud drive. If I run app on real device it works fine, if I run in the simulator (logged with my icloud account) the metadataQueryResults returns always 0 files.
Also the system app "iCloud Drive" cannot fetch or save icloud folders and files.
I tried Debug-->Trigger iCloud sync with no luck.
With xcode 7.2 and any simulator running iOS 8.x or greater worked fine.
Is it a xcode 7.3 bug?
Thanks,
Max
The issue is with OS X 10.11.4. Stay at OS X 10.11.3 or use the 10.11.5 beta.
Yes I got the same problem too after getting the latest Xcode 7.2 -> 7.3.
It looks like a problem with Apples background services crashing in the simulator and not telling its client i.e. the iCloud Drive or your app.
Even triggering an iCloud re-sync doesn't sort it so for the time being we have to debug on a real device which is a pain.
Looking in the system log via the simulator (Debug -> Open System Log), I see a lot of Sandbox (bird) access denied messages from the simulator which I guess are related to the issue - there is more info in some e.g.:
Process: bird [597]
Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/PrivateFrameworks/CloudDocsDaemon.framework/bird
Load Address: 0x1085b8000
Identifier: bird
Version: ??? (???)
Code Type: x86_64 (Native)
Parent Process: launchd_sim [566]
User ID: 501
Date/Time: 2016-04-07 08:28:45.714 +0100
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 8
Thread 0:
0 libsystem_kernel.dylib 0x000000010aae21fa openbyid_np + 10
1 CloudDocsDaemon 0x00000001086f0664 -[BRCRelativePath _resolveAndKeepOpenMustExist:error:] + 872
etc.
I guess there are some permissions that have not been set on the file system that is used on the Mac backend for the simulator, but I've no idea how or what to change.
Do you get the same errors in your log when trying to use iCloud?
The only other thing I did recently was to install the latest Xamarin Studio, I hope that's not related but I doubt it.
Thanks
Matt
I have an application that runs fine on my Win 8.1 development machine but when I go to install it on my Win 7 64 bit test box I run into a TypeInitializationException with Caliburn.Micro.Platform. What could be causing this? the error log that leads me to believe it is Caliburn.Micro is below.
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x30): Windows 7 Professional</Product>
<Edition>Professional</Edition>
<BuildString>7601.18409.amd64fre.win7sp1_gdr.140303-2144</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>2356</ParentProcessId>
<ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
<ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>MyApp.exe</Parameter0>
<Parameter1>0.6.25.0</Parameter1>
<Parameter2>546dfbc7</Parameter2>
<Parameter3>Caliburn.Micro.Platform</Parameter3>
<Parameter4>2.0.1.0</Parameter4>
<Parameter5>53f41236</Parameter5>
<Parameter6>92</Parameter6>
<Parameter7>0</Parameter7>
<Parameter8>System.TypeInitialization</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.256.48</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>2b5c</Parameter22>
<Parameter23>2b5cea20275728230acc663702d2e8da</Parameter23>
<Parameter24>5bd8</Parameter24>
<Parameter25>5bd8dc1fa50918888316b6b5f643c5e9</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID>BA765621-6E94-49A3-BF5C-4CA9CB339779</MID>
<SystemManufacturer>Microsoft Corporation</SystemManufacturer>
<SystemProductName>Virtual Machine</SystemProductName>
<BIOSVersion>090006</BIOSVersion>
</SystemInformation>
</WERReportMetadata>
And you are building against .NET 4.5, and you have the assemblies all correctly referenced. The one that tends to pop out is the Interactivity assembly, it gets buried hard to detected. Since it is a .NET usually version changes between Windows version. Can only suggest it is missing or a version number needed mismatch. Make sure the one from the lib folder in your packages from nuget is present on the install of your WIN7 box. If that is how you got the CM framework. otherwise pull the latest github release
I'm tesing Urduino but can't make it work.
Run urbi.bat
Either run the .u script or loadModule("Arduino");
Error: urbi-launch.exe has encountered a problem and needs to close.
I have tried with Win8 64bit, Win 7 and XP SP3 32 bit. All have the same problem.
Thanks if you can find me a solution.
It's currently only compatible with Urbi 2.7.5 We can use an older Urbi version.