I am receiving a Windows security dialog box when attempting to run a report on a remote server through Jaspersoft Studio. I have done a lot of searching for answers but haven't found anything. Anyone have any ideas of the issue? The remote server is running on Linux, Tomcat6, Jaspersoft Studio installed on WIndows 10, Community Edition of Studio.
This is the dialogue window that comes up in Windows.
Related
Hlo everyone. I want help in connecting mysql with Visual Studio Code. OS- Window
Oracle MySql is already installed in my pc and I want to connect it to VSCode. For that I have also installed MySql Management tool in VSCode.
The problem is that VSCode couldn't find mysql driver.
I have tried my best and checked online solution (Google and YouTube) but all in vain.
I can share my screen so that you can check what's the problem.
I've installed the followings
PowerBI desktop
PostgreSQL
Npgsql v4.1.1 (from https://github.com/npgsql/Npgsql/releases)
Visual Studio 2019 (community)
Even after installing all the above, still I am getting
This connector requires one or more additional components to be installed before it can be used.
Is there anything else, I've to install?
I've re-installed the Visual Studio 2019 and it works.
I installed SSMS 17.9.1.
When I start SSMS it crashes when I try to connect to the database server.
See this 5 second video
https://vimeo.com/302442420/2ed86b92d8
My only action is to click on the "connect" button.
Then the object explorer appears quickly followed by SSMS shutdown.
How can I get SSMS to work properly ?
I asked the same question on the Microsoft Developer Network.
This is the solution that worked:
Uninstall SSMS
Uninstall Visual Studio 2015 IsoShell
Uninstall Microsoft Visual C++ 2015(or 2017 if you are using it) Redistributable. Uninstall both x86 and x64 if they're on your computer.
Reinstall Visual Studio 2015 IsoShell
Reinstall SSMS
Reinstall Microsoft Visual C++ Redistributable
It took a long time!
See this thread.
The goal
I would like to use a Windows Server 2016 (x64) for remote debugging of UWP applications. The reason? My working PC still runs a Windows 7 instance and it is not possible to deploy an UWP app on a Windows 7 machine.
The problem
I have already installed the Remote Tools For Visual Studio 2015 on the Windows Server 2016 machine and started it on port 4020. Authentication mode was set to "None". I have enabled Developer mode on the server as well. Also I have set up my project in Visual Studio to use the remote machine for debugging.
The problem is, whenever I try to deploy (just deploy, not even debug) my solution to the server, the following happens:
Visual Studio shows the following output:
Deploy started: Project: MyProject.UI.Uwp, Configuration: Debug x86
Starting remote deployment...
Reading package recipe file "C:\SourceCode\MyProject\MyProject.UI.Uwp\bin\x86\Debug\MyProject.UI.Uwp.build.appxrecipe"...
and then hangs forever.
In the meantime, remote tools on the server show the following output:
UserAbc connected.
This indicates there must be at least some communication between my Windows 7 PC and the target Windows Server 2016 machine.
No error message is displayed whatsoever (neither in Visual Studio, nor in the Remote Debugger).
The question
Any idea why the deployment hangs forever without an error message? Or am I trying to achieve an impossible task? Is the Windows Server 2016 capable of running UWP apps at all?
Update
I installed VS 2015 Update 3 directly on the Windows Server 2016. I was able to create and debug a simple UWP app directly on the server so the server is clearly able to run an UWP app. However I am still unable to make the remote debugging working. Maybe the problem is completely on my local Windows 7 PC and has nothing to do with the Windows Server. It is strange that the process hangs while "Reading package recipe file". Could it be that an antivirus is intercepting?
Thanks for your feedback. There is a similar issue when I try to deploy the UWP project to a remote machine on Windows 7. We have communicated about this using our internal channel. Unfortunately, Visual Studio 2015 or Visual Studio 2017 doing UWP development on Windows 7 is not a recommend scenario.
For Visual Studio 2017, using Tools for UWP App Development is not applicable on Windows 7. See Visual Studio 2017 Support for Windows Development.
For Visual Studio 2015, the official support for Windows Universal is "Build only". We can use Visual Studio 2015 to build UWP apps on Windows 7, but some other Visual Studio features for Windows Universal development may be degraded. See Visual Studio 2015 Support for Windows Universal, Windows Store, and Windows Phone App Development.
To develop Windows Universal Apps, Windows 10 is strongly recommended. With Windows 10, you can get the best experience of UWP development.
I am using Crystal Reports for Visual Studio 2013. The reports work fine on my local computer and in Visual Studio on the production server.
When I deploy them in IIS 7.5 I am getting the following error:
Failed to open the connection. ReportName
3400_4400_{A861BA52-167D-4EAF-AAAF-32B2FB34FFAA}.rpt
Operating System: Windows Server 2008 R2 Enterprise;
System Type: 64-bit Operating System;
Database: MySQL;
I copied the aspnet_clients folder in the wwwroot folder and in the application folder.
Any help would be appreciated.
Thank you.
There is 2 things which may cause this issue,
Are you installed the Crystal report runtime? if no, then here is
link1, link2. You can choose 64 bit option.
If you installed CR-runtime, then crystal report does not have connect to sqlserver. So for this, if you able to check your local crystal report with prod sqlconnection, check that and still you have issue, means you are not give sql server credential to crystal report at run-time. Check this link.
Crystal Report throws 'Failed to open the connection.' only on postback
http://www.codeproject.com/Questions/667950/crystal-reports-connection-to-sql-server-database
http://aspalliance.com/532_Understanding_the_Login_Failed_Error_in_Crystal_Reports.3
I have some updates!!! I can't believe this was the issue....so frustrating!!!...
On my production server I only created a User DNS...which worked fine with Visual Studio...but not with IIS. After I created a System DNS the report worked fine in IIS as well...