I'm trying to play around with the automatic RDBMS integration. Following the directions in the ignite-web-agent readMe, I copied my postgres driver (42.2.5) into the jdbc-drivers folder.
Ignite and the console agent both started up fine, and the log output from the console agent is below:
[2019-02-12 02:13:10,678][INFO ][main][AgentLauncher] Starting Apache Ignite Web Console Agent...
[2019-02-12 02:13:11,631][INFO ][main][AgentLauncher] Connecting to: https://console.gridgain.com
[2019-02-12 02:13:12,070][INFO ][EventThread][AgentLauncher] Connection established.
[2019-02-12 02:13:12,289][INFO ][EventThread][AgentLauncher] Authentication success.
[2019-02-12 02:13:12,664][INFO ][pool-1-thread-1][RestExecutor] Connected to cluster [url=http://localhost:8080]
[2019-02-12 02:13:12,710][INFO ][pool-1-thread-1][ClusterListener] Connection successfully established to cluster with nodes: [AE9ED479]
Anything I am missing? Any ports that I need to confirm are open?
I am running:
- Cloud platform: AWS
- OS: Windows Server 2019
- DB: Posgres 11.1
- DB Driver: PostgreSQL-42.2.5.jar
- Java: 1.8.x.202
- Ignite: 2.7
- Ignite-Web-Agent: 2.7.1
Thanks!
PostgresSQL server should run on same machine where Web agent launched.
Go to console.gridgain.com and click "Import from Database" (at the top-right corner). It will open "Model import" dialog where you should be able to import model from your DB in step-by-step wizard.
See docs (with a bit outdated screenshots, but general the same).
Hope this help.
Update 1.
After some thoughts, I think #1 is not a "must have", but instead should be treated as "Web Agent should be able to connect to RDBMS via JDBC driver". Usually it is easy to do when Web Agent and RDBMS server run on same machine, but should work in more general case.
Related
I am facing a problem that when i try to configure my TFS it show me the following Error Message
Error
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you are attempting to connect to is online, and that you have the required permissions to connect. If you are attempting to connect to the remote SQL Server instance, then verify that it is configured to allow remote connections, that TCP/IP protocol is both enabled and configured to use port 1433 (default), and that Windows Firewall does not block this port.
Check whether the SQL version is supported by the TFS version: https://www.visualstudio.com/en-us/docs/setup-admin/requirements#sql-server
Check the permission of the account that you use, and make sure it belongs to SysAdmin Server Role.
As #Daniel mentioned in comment, follow the troubleshooting steps provided in the error message, and check this blog to see whether it is helpful: https://elhajj.wordpress.com/2013/02/25/workaround-error-tf255049-punching-a-hole-through-windows-firewall/
I was running an upgrade from TFS 2018 to Azure DevOps 2020.
After the server restart, the Azure DevOps Server Configuration wizard opened.
I was logged in as the local machine administrator and got this error (TF255049: A connection cannot be made to the server that is running SQL Server...) when trying to connect to my SQL Server machine (to chose the configuration database).
I logged in as Network Administrator, started the wizard again and the SQL connection worked.
To restart the Azure DevOps Configuration Wizard again...
Open the Azure DevOps Administration Console and choose Configure Installed Features to open the Server Configuration Wizard...
I have an Azure web app that has some Hybrid Connections setup. I'd like to be able to prove they are working from the KuDu cmd interface.
Unfortunately telnet is not installed as part of the Azure WebApp OS (Win Server 2012) and I seem to have limited permissions.
Can anyone help?
Specifically I want to make sure I can relay to an email server, so telnetting to the port would be very useful.
Kind regards
Si
Can you try tcpping instead? tcpping is installed and available for use from the Kudu console.
I am not able to connect to the database engine. I have recently installed SQL Server 2012 after formatting my hard drive.
Operating system : Win 7 Enterprise 64-bit
When I try to connect to the database engine :
WN7X64-XXXXXXX, I get the following error message
A network-related or instance-specific error occured. Could not open connection to the SQL Server'.
I tried accessing using (localhost). It did not work.
I tried accessing using (localhost)/SQLExpress. It did not work.
I tried accessing using (localhost)/MSSQLServer. It did not work.
I tried accessing using MSSQLServer. It did not work.
When I checked the services. SQL Server status is starting, and it does not give me the option to start/stop. SQL Server Agent status is blank, when I start the service it gives
Error 1068 : dependency service or group failed to start.
Name Status Startup Type
SQL Full-text Filter Daemon Launcher (MSSQLSERVER) Started Automatic
SQL Server (MSSQLSERVER) Starting Automatic
SQL Server Agent (MSSQLSERVER) Automatic
SQL Server Analysis Services (MSSQLSERVER) Started Automatic
SQL Server Browser Started Automatic
SQL Server Distributed Replay Client Started Automatic
SQL Server Distributed Replay Controller Started Automatic
SQL Server Integration Services 11.0 Started Automatic
SQL Server Reporting Services (MSSQLSERVER) Started Automatic
SQL Server VSS Writer Started Automatic
I sometimes get SQL Server Express stuck in 'starting', in fact, just now, which is why I googled up this page. The solution is to kill the process and restart it.
Simplest way to do that is through Task Manager, which you can start by right clicking the Windows system tray (banner at the bottom of the screen where minised programs go). Processes tab, Sort processes by Name, find all beginning 'SQL...' and stop them.
To restart SQL Server right click the Windows Start button, start Control Panel, Administrative Tools, Services, scroll to all services starting 'SQL...', right click to refresh, and stop any that are running, then start the 'SQL Server' service, followed by any others that are set to Auto or Manual start.
I had the same issue and MSDN Documentation did not help. https://support.microsoft.com/en-us/kb/307288.
It was to do with that there was an orphan Sql related service i.e SqlWriter was hanging around. Go to task manager and killed it. Then the error went away.
To connect to a SQL Server default instance (not Express), you can use:
just a . (dot)
just a (local) (be aware: in round brackets)
just a localhost (be aware: NO brackets)
See the official MSDN documentation on Logging In to SQL Server for more details and explanations, and for even more options how to connect.
Try localhost or (local). Not (localhost).
I had the same issue . go to task manager , search for "SQL Server Windows NT" then end the task . after that , go to your services (Run services.msc) and restart your sql server instance .
Solution works for me in MSSQL Server express edition with Windows 10 environment .
Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.
I am trying to connect Jprofiler7 to remote weblogic10.3 managed servers. I am able to connect and see admin console threads and memory usage in JProfiler but not for application deployed on managed server.
How can i achieve this?
Thanks
I had the same problem with WebLogic 12C on windows with JProfiler9 and solved it as follows:
Allow JProfiler to create startWebLogic_jprofiler.cmd by profiling WebLogic 12C, but don't attach the profiler at this point.
Edit startManagedWebLogic.cmd and call startWebLogic_jprofiler.cmd rather than startWebLogic.cmd
At a command prompt execute startWebLogic.cmd
At a command prompt execute startManagedWebLogic.cmd
In JProfiler, click "Start Center" icon. Click "New Server Integration". Select "Generic application server" and then "Wait for a connection from the JProfiler GUI". When the profiler starts it collects data from the managed weblogic server.
You're profiling the wrong server in that case. The VM parameter for JProfiler (-agentpath:...) has to be added to the JVM on which your application is executed.