Im trying to start virgo server with vsphere sdk version 6.7 in my local machine and getting this error.
λ startup.bat
WARNING: jmxPermissions.vbs did not update the permissions of \vSphere Client SDK\html-client-sdk-6.7.0-8170180\vsphere-ui\server\configuration\org.eclipse.virgo.kernel.jmxremote.access.properties. Check the file has the correct permissions.
'Client' is not recognized as an internal or external command,
operable program or batch file.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Error: Could not find or load main class Client
The issue is that you have deployed the SDK on a Windows path with spaces - startup.bat thinks " Client SDK\html-client-sdk-6.7.0-8170180\vsphere-ui\server\" is a command line argument.
The simple fix is to move the SDK to a location without any spaces.
Kudos goes to my colleague Alex Marinov (https://www.linkedin.com/in/aleksandar-marinov/) for spotting this.
Related
I'd like to schedule a KNIME workflow. The workflow does its job very good as long as I start it from the KNIME GUI application. When I execute the same workflow via command line, java complains that com.microsoft.sqlserver.jdbc.SQLServerDriver
could not be found (ClassNotFoundException).
I invoke it via:
"D:\Progamme\KNIME\knime.exe" -nosplash -application -consoleLog org.knime.product.KNIME_BATCH_APPLICATION -preferences="absolutepathto\preferences.epf" -workflowDir="absolutepathto\workflow"
Since the error message signals missing content in the java CLASSPATH I also tried to add the parameters
-vmargs -classpath .;"absolutepathto/sqljdbc42.jar"
But still I earn a java slap, pointing to the same error...
I also tried to run the command from within the knime.exe's directory and I also tried to add the JAR file to Preferences -> Java -> Build Path -> Classpath Variable / User Libraries (referenced via the -preference argument). But that had no effect.
Did anybody face the same problems? Maybe with other third party JARs?
It is all about a Database connector that is configured like this:
Does the integrated security maybe force a misleading error?
System spec: KNIME 3.2.2 on Windows Server 2008 R2
Update - extract from preferences file
/configuration/org.eclipse.core.net/org.eclipse.core.net.hasMigrated=true
/configuration/org.eclipse.ui.ide/MAX_RECENT_WORKSPACES=10
/configuration/org.eclipse.ui.ide/RECENT_WORKSPACES=<list of some workspaces>
/configuration/org.eclipse.ui.ide/RECENT_WORKSPACES_PROTOCOL=3
/configuration/org.eclipse.ui.ide/SHOW_RECENT_WORKSPACES=false
/configuration/org.eclipse.ui.ide/SHOW_WORKSPACE_SELECTION_DIALOG=true
Is there maybe a problem due to the fact that it is a shared KNIME instance among several users and the command line execution does not know which workspace has to be chosen? Is the workspace somehow needed and why?
Partial Solution:
I finally managed it but I don't know exactly why it works now. What I did was to load a fresh portable version of KNIME and ran the same commands only changing the executable path to the new portable version. Before that I started the portable version once to set the workspace directory and register the database driver in preferences dialog and .ini file, nothing else, same configuration so far as the shared KNIME instance. What I am really wondering abpout is that from now on the commands are also working with the shared KNIME instance. I really don't know what caused the change that let KNIME find the driver class.
Info
Because I encountered a few more problems within shared environment in KNIME command line mode, that led to undeterministic execution results, I wrote a little .NET library. This gives me more flexibility/control over the workflow execution (which returncodes and error messages occured and so on). You can find it here if you're interested: KnimeNet
I took a very minimal approach:
cd "C:\Program Files\KNIME"
.\knime -nosplash -noexit -consoleLog -reset -application org.knime.product.KNIME_BATCH_APPLICATION -workflowFile="D:\Work\Knime Workflows\Output\CMD_Test.knwf" -preferences="D:\Work\Knime Workflows\Output\CMD_Test.epf"
I am trying to convert to UWP my desktop application Computator.NET (written in WinForms) which is using InstallShield for it's installer but DAC does not seem to find executable. It looks like it thinks that exe file is some temporary installer file. Log from the process is below:
WARNING: DesktopAppConverter : warning 'W_PACKAGE_DEPENDENCY_ADDED': A
dependency on framework package 'Microsoft.VCLibs.140.00.UWPDesktop'
was added to the AppxManifest.xml. See
'http://go.microsoft.com/fwlink/?LinkId=821959' for guidance on
installing the package prior to local deployment. Otherwise, if this
is in error, remove the corresponding entry from Dependencies in the
AppxManifest.xml before packaging and deploying your application.
WARNING: DesktopAppConverter : warning 'W_DISCOVERED_EXE_NOT_FOUND':
Discovered shortcut indicates the app executable should be
'\WINDOWS\Installer{FA089B43-0451-420A-968B-DCC3C55644C7}_8C37B49DBB16422C8EF917F2AEA02293.exe',
but this file cannot be found. WARNING: DesktopAppConverter : warning
'W_DISCOVERED_EXE_NOT_FOUND': Discovered shortcut indicates the app
executable should be
'\WINDOWS\Installer{FA089B43-0451-420A-968B-DCC3C55644C7}_A9A8E5CA913F4E1EB7F6ACDB86DAFB8B.exe',
but this file cannot be found. WARNING: DesktopAppConverter : warning
'W_DISCOVERED_EXE_NOT_FOUND': Discovered shortcut indicates the app
executable should be '\Windows\SysWOW64\msiexec.exe', but this file
cannot be found. WARNING: DesktopAppConverter : warning
'W_EXE_NOT_DISCOVERED': The application executable could not be
determined from any shortcut. MakeAppx will fail until you fix the
Application Executable property in the AppxManifest.xml WARNING:
DesktopAppConverter : warning 'W_INSTALL_PATH_NOT_DISCOVERED':
Converter could not determine your application's install path. Please
use the -AppInstallPath parameter to move app binaries outside of VFS.
WARNING: DesktopAppConverter : warning
'W_CANNOT_MAKEAPPX_WITHOUT_EXE': Unable to create appx package without
setting the 'Application Executable' property in the AppxManifest.xml.
Please set the 'Application Executable' property in the
AppxManifest.xml before calling makeappx manually. Warning Summary:
W_PACKAGE_DEPENDENCY_ADDED A dependency on framework package
'Microsoft.VCLibs.140.00.UWPDesktop' was added to the
AppxManifest.xml. See 'http://go.microsoft.com/fwlink/?LinkId=821959'
for guidance on installing the package prior to local deployment.
Otherwise, if this is in error, remove the corresponding entry from
Dependencies in the AppxManifest.xml before packaging and deploying
your application.
W_DISCOVERED_EXE_NOT_FOUND Discovered shortcut indicates the app
executable should be
'\WINDOWS\Installer{FA089B43-0451-420A-968B-DCC3C55644C7}_8C37B49DBB16422C8EF917F2AEA02293.exe',
but this file cannot be found.
W_DISCOVERED_EXE_NOT_FOUND Discovered shortcut indicates the app
executable should be
'\WINDOWS\Installer{FA089B43-0451-420A-968B-DCC3C55644C7}_A9A8E5CA913F4E1EB7F6ACDB86DAFB8B.exe',
but this file cannot be found.
W_DISCOVERED_EXE_NOT_FOUND Discovered shortcut indicates the app
executable should be '\Windows\SysWOW64\msiexec.exe', but this file
cannot be found.
W_EXE_NOT_DISCOVERED The application executable could not be
determined from any shortcut. MakeAppx will fail until you fix the
Application Executable property in the AppxManifest.xml
W_INSTALL_PATH_NOT_DISCOVERED Converter could not determine your
application's install path. Please use the -AppInstallPath parameter
to move app binaries outside of VFS.
W_CANNOT_MAKEAPPX_WITHOUT_EXE Unable to create appx package without
setting the 'Application Executable' property in the AppxManifest.xml.
Please set the 'Application Executable' property in the
AppxManifest.xml before calling makeappx manually.
I am runing Dekstop App Converter using fairly simple command:
DesktopAppConverter.exe -Installer C:\Computator.NET\Computator.NET.Installer.v2.1.0.beta.exe -InstallerArguments "/S" -Destination C:\Computator.NET\Appx -PackageName "Computator.NET" -Publisher "CN=Pawel Troka" -Version 2.1.0.0 -MakeAppx
It seems like this issue is because of the way InstallShield installer is working.
Fortunetely there is an easy way to resolve this - we need to pass path to executable, just like it -AppExecutable "path_to_your_exe_file_after_installation"
So my final command looked like this:
DesktopAppConverter.exe -Installer
C:\Computator.NET\Computator.NET.Installer.v2.1.0.beta.exe
-InstallerArguments "/S" -Destination C:\Computator.NET\Appx -PackageName "Computator.NET" -Publisher "CN=Pawel Troka" -Version 2.1.0.0 -MakeAppx -AppExecutable "C:\Program Files (x86)\Computator.NET\Computator.NET.exe" -Sign
Note that I also added -MakeAppx and -Sign arguments, this is because I wanted it to be ready for testing - just needed to install certificate auto-generated.cer to Trusted Root Certification Authorities after conversion and my appx was ready to be installed and tested on my developer machine.
This tutorial was really helpful during the process and also this article helped me a bit.
I have installed the solr service on a LINUX environment. Now trying to start the service using the below command
service solr start
After executing this command, am getting below error from the server
Waiting to see Solr listening on port 8080 [-] Still not seeing Solr listening on 8080 after 30 seconds!
tail: cannot open `/var/solr/logs/solr.log' for reading: No such file or directory
I created the solr.log file manually and placed it under the above mentioned path, But as soon, i issue the command "service solr start" . The solr.log file will be renamed and there won't be any new file created with the solr.log. hence the service fails to start. Could anyone let me know how to tackle this issue.
Thanks in advance.
I had a similar issue, and was able to find a hint in the /var/solr/logs/solr-8983-console.log
Originally I had been using Java 8, and Solr was working just fine for me.
When I switched to Java 11, Solr would have the issue you reported.
The log file contained the following:
Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I switched back to Java 8 and Solr started just fine.
First, did you use the procedure provided to install the Solr service page 461
Second, did you set the proper overrides to the environment defaults in a solr.in.sh script (p. 462 of the ref manual). You also need to make sure that the LOG4J_PROPS in the solr.in.sh file points to your log4j.properties file. Also make sure that SOLR_LOGS_DIR is pointing to the correct place.
If all that is correct, then check that the values in your log4j.properties file are set correctly (p. 468 of the ref manual).
You can get the reference manual here: https://www.apache.org/dyn/closer.lua/lucene/solr/ref-guide/ if you don't have it already.
I had a tough time getting Solr to run as a service, but in the end I simply wasn't reading carefully enough.
I have few Ordered tests which I execute locally using the VSTEST.CONSOLE.EXE In a batch file. I want to launch this batch file from remote system on about 15 VMs. I have the desktop active on all the VMs and user under which these test cases need to be executed are also same as the user logged in. When I try to execute the batch file using the PSExec it throws an error and dosent launch the tests the error shown is as below
C:\TestRunningFolder>vstest.console.exe C:\BuildsFolder\BVTTests.orderedtest /Settings:C:\BuildsFolder\QuestCodedUI.testsettings /Logger:trx
Microsoft (R) Test Execution Command Line Tool Version 12.0.30723.0
Copyright (c) Microsoft Corporation. All rights reserved.
starting test execution, please wait...
Warning: Warning: Test Run deployment issue: The assembly or module 'UiaComWrapp
r' directly or indirectly referenced by the test container 'c:\BuildsFolder\questcodedui.dll' was not found.Error: Test host process
exited unexpectedly.
Error: Failed to queue test run 'testuser#RemoteMachine 2015-05-14 15:57:49':
Unable to start the agent process.
Please let me know how can I execute the CodedUI tests on remote machine without using the TestAgent/Controller. Is it possible Via WMI ?. Anyone tried and succeeded please let me know.
Update : I was able to get past this issue by copying the required files in the folder. Now I am trying to launch the CodedUI tests using the PSExec.exe on remote system. I have remote desktop active and when I try to launch the batch file using the command line and it just gives me a message as shown below. PSEXEC.EXE \RemoteMachinename -i "c\users\testuser\desktop\Runtests.bat" when I do that it returns with error code 1 and tests are not started yet. I tried searching for solution I couldn't find anything that is usefull.
For the above mentioned scenario, please copy all the dependency dll (eg : Microsoft.Visualstudio.Qualitytools.CodeduiTest etc.) to the folder where your build dll (projectname.dll) file is copied. Make sure that you are using correct version of vstest that supports the version of the VS you are using. For example, if your code is builded using VS 2015, you have to use vstest.console.exe that comes with Test Agent 2015/Test Agent 2013 Update 5. This trick worked for me. Please let me know whether this works for you. Regards.
I need to run Jboss 7 as service.
Followed these steps :-
Copied my Jboss to C:\Program Files <86>
Downloaded Jboss-native-2.0.10-windows-x64-ssl and copied the contenst of bin catalog to %JBOSS_HOME%/bin
Changes done on service.bat as per link instructions
https://community.jboss.org/message/724488
Changed my dir location to my Jboss bin
and given command service.bat install
C:\Program Files \jboss7>bin>service.bat install
Failed installing JBAS50SVC
Access is Denied.
Service JBoss Application Server 7.1.1 installed.
I'm not able to rectify this problem .
It appears to be windows access issue.
Try the following:
Does the windows ID you are using have Administrator privileges? If no, get a Admin ID else if Yes, proceed to step 2.
Try to do the same but in some other drive (not c: )
UPDATE #1 : OP says he can not see the output of service.bat file
Follow the following steps
Open start menu
Search for "cmd"
Right click "cmd" and run as Administrator
type in following command
cd C:\Program Files \jboss7\bin
Type service.bat and observe the output
On a 2008 Windows Server this occurs because you're not running the command line as an administrator. Those of us who have spent considerable amounts of time on 2003 server, and others before that, keep forgetting that your logged in ADMIN level account does NOT get passed to the command line automatically like with previous versions of Windows.
With any additional errors, past this one, I would keep going back to the service.bat file and looking at the path statements, throughout that file, to ensure that they are all correct to reach what is correct for your installation.
Also, don't forget to create a log folder under standalone (unless you're doing a domain install). Failure to do that will also cause issues as well.
yoda