|
Hi all, when i build an installation package with the deployment wizard scjview.exe and dbisql.exe do not start after installing this package on a blank system. Has there something changed regarding java or so? Thanks, Axel |
|
This works again with 17.10.6160 👍🏼 So feel free to accept an answer then... :)
(07 Aug '20, 07:37)
Volker Barth
Sorry, i don't understand, Volker. 😟 Just like i don't understand the working method of this forum, i'm afraid.
(07 Aug '20, 07:44)
Axel Siepmann
Replies hidden
1
> Just like i don't understand the working method of this forum, i'm afraid. You seem to be doing pretty well. Since you asked the question, you can click on the grey checkmark icon in the top left corner of one of the answers (like this one) to mark it as an "accepted answer". The "faq" link in the top right corner of the page will answer some of your questions... but not all; it's not a comprehensive source. One of the trickiest items is the tiny "box-with-arrow-icon" underneath each comment entry... you click on that to post a nested "comment on a comment", as opposed to clicking on "add new comment" like you did here (which posted a top-level comment). FWIW this forum uses a GUI that is very similar to the one used by stackoverflow.com several years ago, before that website became unfriendly.
(07 Aug '20, 09:32)
Breck Carter
|
|
I suspect that this issue is because the install is missing msvcr120.dll (and possibly msvcp120.dll) that is required by the new SAP JVM introduced in 17.0 Build 5745. As a workaround, you can modify the wizard's master.xml to add the library(s) to the install once those files are copied into the java BIN directory. For example: Locate the following and create a similar entry for v12 (you may need to do the same for 32 bit) lib path="[BIN64_DIR]\jre180\bin\msvcr100" *** *** The tag was not posted as it is being stripped. Use the same formatting as the master.xml. Add: lib path="[BIN64_DIR]\jre180\bin\msvcr120" lib path="[BIN64_DIR]\jre180\bin\msvcp120" ** You will need to ensure the files are copied into the BIN directory referenced. Alternatively, you can install the runtime for that version which will install to Windows\SYSTEM32 which is already on the path. Thanks, Chris! I managed to build a working installation. Hope this issue will be fixed in an upcoming build.
(03 Feb '20, 08:20)
Axel Siepmann
|
|
FYI 2837154 - Deployment Wizard creates incomplete MSI - SQL Anywhere 1
Workaround from "2837154 - Deployment Wizard creates incomplete MSI" Follow the following steps as a workaround for this problem:
Download the Visual Studio 2013 Redistributable package from Microsoft or copy them from C:\Windows\System32
Search for msvcr100.dll in the XML file and update the file with msvcr120.dll and msvcp120.dll at all the places with msvcr100.dll functions.
(28 Jan '20, 07:13)
Breck Carter
|
|
Still doesn't work with 17.10.6057... The fix was completed after this build. It will be in the next update 17.0 Build 6061 or newer.
(12 Mar '20, 09:22)
Chris Keating
Ok, thanks for you quick response, Chris. I'll be patient. :-)
(12 Mar '20, 09:25)
Axel Siepmann
This issue still appears to be happening even with 17.0.10.6089, even though the Readme appears to include it in with Build #6062 - Engineering Case #821072. I'm still getting the following errors when I attempt to run SQL Central 17.0.10.6089. The errors do not always occur immediately, sometimes they occur a few minutes after starting up and I can actually begin to use SQL Central before it crashes. I've tried copying over the dll's described above into the BIN64 and BIN64\jre180\bin folders, but that has not helped me. The error popups I see are as follows: LoadLibrary failed with error 87: the parameter is incorrect. Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Program Files\SQL Anywhere 17\BIN64\scjview.exe R6025 - pure virtual function call
(08 Jun '20, 15:50)
tsinnott
This is not the same issue as described in this thread. I have seen this error once before (late 2018) with Sybase Central but we were never able to reproduce or confirm a solution. The error that you are seeing "LoadLibrary failed with error 87" is commonly related to a file called atig6pxx.dll. If you search for "LoadLibrary failed with error 87" there are recommendations to rename the atig6pxx.dll if it exists and update/reinstall the graphics driver if based on ATI/AMD graphic chips. Do you have a crash log in the SQL Anywhere diagnostics directory for this issue? A capture of this behaviour with SysInternals Process Monitor in an effort to determine what DLL is failing to load with that error might be useful. If you have technical support, you may want to consider opening an incident to help with the review of any crash log and the process monitor output that is collected for this problem. If you want to continue in this forum, I would recommend that you start a new question since the problems are different.
(08 Jun '20, 16:37)
Chris Keating
Replies hidden
@Chris: You can use "Convert comment to question" on the OP's comment, but then you will have to manually move your comment to the new question because you posted it as a comment on the old question rather than a reply to the OP's comment... ...if any of that makes sense :)
(09 Jun '20, 07:54)
Breck Carter
In my experience, it's easier to turn single comments into new questions and then to "add" comments there. My attempts to turn nested comments into new questions (though logically more appropriate) usually forced me to contact the forum administrators to fix what went wrong duringt the move...
(09 Jun '20, 08:10)
Volker Barth
1
@Chris: Thank you for the response and advice. I'm new to this forum and the issue described on this question seemed very similar to what I’d been seeing so I thought it was related. Your comments about updating the display adaptor lead me to check if there were any updates available for it. There weren’t but I did then realize that we’re on Windows 1809 still and corporate does not always push out the latest updates through the Windows Update (WSUS) process on a very timely basis. So even though I was up to date with the corporate WSUS, I decided to “Check online for updates from Microsoft Update” and sure enough there were some pending updates for Windows 1809 available there. Once those updates were installed, the problem with SQL Central seems to have gone away. Since it’s corrected for us now, I won’t open a new question. Thanks for the help.
(09 Jun '20, 12:37)
tsinnott
|
The latest build with wich i can build a working installation is 17.09.4935. All later builds throw errors when running scjview.exe or it simply does not start.