So, I've got a problem, similar to this one, but with a WebApplication running with JBoss on RHEL: How to install SQLite JDBC Driver? but I cannot find a solution.
My problem is: If I build my code with IntelliJ I can run it locally (A Windows PC) but can't run it under a RHEL server. It throws: "java.sql.SQLException: RouteToMyDataBase"
However if I build my code with NetBeans it run's under both OS (RHEL and Windows), sooo, I don't think my code's wrong at all and I think there's something to do with my classpath, or the way I'm building my "artifacts" with IntelliJ.
I tried by copying my libs inside /opt/jbosseap51/jboss-as/server/default/lib/ as suggested somewhere else here (I lost the Question)
Please, don't tell me to build my project with netbeans, because it is a huge application build using intelliJ and would be too difficult to migrate all the project. It is working ok, but recently while migrating our project to different machines through SVN happend this.
¿Is there anything else I have to configure?
Related
Feels like a silly question, but I'm struggling to find the answer online: Is it possible to deploy Qt apps to Windows if you did development on a Linux machine? It seems the answer should be "yes", but I can't seem to use windeployqt on my linux machine.
If it is possible, what additional resources do I need to do this?
Yes, it's of course possible.
You have to cross-compile Qt using the MinGW compiler, targeting Windows.
You'll have to patch and build windeployqt yourself. By default, windeployqt is looking for g++.exe in the path. Of course this makes no sense on a linux build host, so you'd have to tweak it so that it finds the correct compiler and runtime libraries.
You can then build your application using the cross-targeted Qt build, and deploy all the necessary artifacts into some deploy folder using windeployqt.
To package the deployed build, you can run nsis or wix on Linux as well, to obtain a Windows installer. You can even sign the executable files (required these days for Windows), there's an open source tool called osslsigncode - it works on most platforms and doesn't require Windows.
It'll take a bit of time for you to figure it all out. It's certainly easiest to just build on Windows and not mess with it. But if you insist on building on Linux - you certainly can.
I am creating an ASP .Net Core (2.0) MVC application within Visual Studio 2017 which was working absolutely fine.
After turning off my computer yesterday and coming back to my application today, I now receive this browser error when I start the application in chrome without debugging.
Running dotnet run within the directory of the application, I can access the site just fine. It is just when I run it via Visual Studio/IIS Express I get this error.
HTTP Error 502.5 - Process Failure
The application builds and compiles just fine. I have also cleaned the solution.
Looking in the event logs I find:
Application 'MACHINE/WEBROOT/APPHOST/MYAPP' with
physical root 'C:\Users\Ben Hawkins\Desktop\Development Folder
\Dev\Website\Version_2\MYAPP\MYAPP\'
failed to start process with commandline 'C:\Program Files
(x86)\Microsoft Visual
Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Web
Tools\ProjectSystem\VSIISExeLauncher.exe -argFile "C:\Users\Ben
Hawkins\AppData\Local\Temp\tmp3547.tmp"', ErrorCode = '0x80004005 :
0.
Within my output window in Visual Studio 2017 I recieve this message under
ASP NET CORE WebServer
Failed to initialize CoreCLR, HRESULT: 0x80131534
What I have tried:
Cleaning the solution, rebuilding etc
Restarting the computer
Trying to launch another application. (Same result)
Created a new application from scratch. Same result.
Repairing Visual Studio Community 2017. Same result.
Stopping/Closing IIS Express
My setup was working perfectly yesterday and suddenly is not.
Thank you for your time. I hope we can find a solution.
We finally found the issue! After logging on to the machine as a different user, we saw a warning that the main user had ignored initially. There was a 0 byte file in the root of the directory named "Program" with no file extension. It appears that this causes some sort of issue when VSIISExeLauncher.exe is invoked through Visual Studio. (Note it would work if executed from the command prompt). After deleting the file, everything worked!
We do not know how this file was placed there for certain, but suspect it was some sort of copy error when the user was pulling in files from his old hard drive.
I don't know if anyone else will come across this, but if so hopefully this helps!
Maybe you need install previous versions of .NET Core, isn't it? I installed here and it works now. I had only .NET Core 2.0 installed and I realized that applications with 1.1 stopped so when running. In Windows' event logs I've had the same error registered.
Try to change the IISExpress to IIS by creating new IIS profile and change the Lunch to IIS. It resolved my problem.
I have hit a very similar issue with ASP.net Core 2.0. I had copied my VS project to a new one, and I was getting this error message.
After doing some research, I was able to determine that the nlog.config file was not copied into the bin > Debug > net461 folder. Once I did this, I was able to run my application.
I found it by running dotnet run from the command line on my project where the csproj files live.
Had same issue yesterday (windows 10).
Solved it this way:
Update Microsoft.AspNetCore to latest (Nuget manager - 2.1.3)
Make sure the sdk also updated to latest version. if not, update it manually from Nuget console like this:
Install-Package Microsoft.NETCore.App -Version 2.1.3
Download and install latest ASP.NET Core/.NET Core: Runtime & Hosting Bundle
from here
Same problem with version 2.2. Reinstalling .NET Core SDK fixed the problem for us.
In my case, my project was setup as a website in IIS and the file "bin\IISSupport\VSIISExeLauncher.exe" was missing in the project's directory.
I simply selected "IIS" when debugging the project in Visual Studio 2019 and it generated the missing file. It also generated 2 text files (IISExeLauncherArgs.txt, pidfile.txt) in the IISSupport folder, made changes to my web.config file, and my project ran successfully.
After that I was able to access the local website that was setup in IIS without running it in Visual Studio.
Im mostly an frontender, so Im pretty satisfied with that I even got ASP.NET up and running on my Mac. What I think I have done is installing all things necessary to run a project. At least I can now create a project with
yo aspnet
and run it with
dnx web
I can also see the scaffolding created by Yeoman in Visual Studio Code. Everything is fine.
My problem is, when Im trying to run a project that one of the Windows developers have asked me to work on. I clone the repo but when I try to run dnx web is says:
Error: Unable to resolve project from /Volumes/Diverse/Doks/Erhverv/Kimik IT/git-repo/XYZ
I also notice that there is no project.json or startup.cs-file in the project. It looks like this:
http://oi64.tinypic.com/21bvqfk.jpg
Its a site with Composite C1 CMS - what do I need to do to be able to run it on localhost:5000 ?
Every input much appreciated.
You can't, C1 5.0 requires full .net framework 4.5.1 which only runs on Windows, so neither Mono og Asp.Net Core will work.
See also https://github.com/Orckestra/C1-CMS/issues/94#issuecomment-206229567
I've got an application using sqlite that works fine when running it through the compiler. (Both debug and release more). However when I try to deploy it with macdeployqt I get the following error:
ERROR: no file at "/opt/local/lib/mysql55/lib/libmysqlclient.18.dylib"
When trying my app on a mac that does not have Qt installed it crashes randomly after a few minutes.
Any ideas? I am not using mysql in my app just sqlite.
I think you need to build sql plugin at first.
I'm using a trial version of TestComplete 8.70.720.7 for test automation. I've faced a problem with breakpoints - they don't work even if test debugging is turned on. What can be the reason of the problem?
TestComplete uses the Microsoft Script Debugger to debug JScript and VBScript scripts. So, this functionality depends on the MS script debugging components installed on your computer. If the break points are not working, there is something wrong with the script debugging components - TestComplete can't use them for some reason. There are multiple reasons for this problem to occur. Many of them are described in the following FAQ entry in the SmartBear Support Portal:
http://support.smartbear.com/viewarticle/8874/
If the suggestions from that article do not help, this may mean that you have faced a situation when TestComplete is trying to use the Script Debugger installed with Visual Studio. At that, not all versions of the VS Script Debugger are compatible with TestComplete. So, if you have VS installed on your PC, try doing the following:
Close Visual Studio and TestComplete.
Rename the VS7Debug folder on your disk (the path to it looks like this: C:\Program Files\Common Files\microsoft shared), to something else like "_VS7Debug".
Reinstall the Microsoft Script Debugger using the link from the FAQ article above. When installing under Windows 7, Vista, or Win Server 2008, run the installation with elevated permissions (use the "Run As Administrator" context menu command).
Does this fix the problem?