Facing Error: *cannot start the server 'servername' *
when trying to start the workflow, iam getting the above error. I have configured server settings properly and it resolved as well..
all the informatica services are running fine. what could be the problem.
I suspect this as a wrong assignment of Integration service to workflow.
Make sure you assign a running/working Integration service to the workflow.
To assign a Integration service, Close all folders and select the Integration server from the navigation panel and select the workflow which you are trying to run and apply the settings.
Let me know if this works for you.
which version are you running ?? there could be multiple reasons for this error message, but most probably -
your informatica server configuration is not correct, and therefore the attempt to start the server fails. As a result, when a workflow tried to execute, the attempt to connect to a running server instance fails.
I doubt if all the infa services are running fine.. if actually so, then I would reconfigure my client connection and see if you are actually hitting the right domain/service combination.
I feel there can be multiple reason for this issue
Informatica Integration services is not correctly assinged
Informatica services is not running
wrong connection
I believe informatica integration services related issue will be there.
Related
I am attempting to take my existing cloud composer environment and connect to a remote SQL database (Azure SQL). I've been banging at my head at this for a few days and I'm hoping someone can point out where my problem lies.
Following the documentation found here I've spun up a GKE Service and SQL Proxy workload. I then created a new airflow connection as show here using the full name of the service azure-sqlproxy-service:
I test run one of my DAG tasks and get the following:
Unable to connect: Adaptive Server is unavailable or does not exist
Not sure on the issue I decide to remote directly into one of the workers, whitelist that IP on the remote DB firewall, and try to connect to the server. With no command line MSSQL client installed I launch python on the worker and attempt to connect to the database with the following:
connection = pymssql.connect(host='database.url.net',user='sa',password='password',database='database')
From which I get the same error above with both the Service and the remote IP entered in as host. Even ignoring the service/proxy shouldn't this airflow worker be able to reach the remote database? I can ping websites but checking the remote logs the DB doesn't show any failed logins. With the generic error and not many ideas on what to do next I'm stuck. A few google results have suggested switching libraries but I'm not quite sure how, or if I even need to, within airflow.
What troubleshooting steps could I take next to get at least a single worker communicating to the DB before moving on the the service/proxy?
After much pain I've found that Cloud composer uses ubuntu 1804 which currently breaks pymssql as per here:
https://github.com/pymssql/pymssql/issues/687
I tried downgrading to 2.1.4 to no success. Needing to get this done I've followed the instructions outlined in this post to use pyodbc.
Google Composer- How do I install Microsoft SQL Server ODBC drivers on environments
I am facing below error when starting the PowerCenter Integration service on Informatica 9.6.1, the service fails and the following error message is displayed.
ERROR: "Unable to handle request because repository content do not exist" when starting the Integration service.
I have done research and i have changed the Repository to run Normal Mode and i have restarted both the Repository and Integration Services, but still it is not resolved.
Can anyone help on this please.
Sometimes small actions makes a big impact, please try to restart your machine. This looks like you have installed the software and never restarted the machine.
Repo > Repository Properties > Operating Mode
Change this option from "Exclusive Mode" to "Normal Mode" and restart both Repository and Integration Services.
I am trying to test WCF endpoint stress testing using VS 2013 Cloud Load testing. I have created unit testes which are running fine. To make my unit test work I had to pass some random set of values to the endpoint. So I created a database haavinf with valid values and randomly selecting them as a input for my WCF endpoint.
I am trying to use VS 2013 Cloud load testing and my tests are failing at Unit test Initialization test.
Initialization method WCFLoadTests.Tests.Init threw exception.
System.Data.Entity.Core.EntityException:
System.Data.Entity.Core.EntityException: The underlying provider failed on Open. --->
System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
Do I need to do some setting on cloud? or what?
Many thanks,
Thanks all who read my question and spent their time to help me resolve it.
I have fixed this issue by simply using Code First technique in my Unit Tests. Earlier I was using Database first ( was being Lazy) and generated connection string ( providerName="System.Data.EntityClient" ) was giving error.
Many thanks,
I need a little help solving an issue regarding .NET web services. I have a desktop application that consumes my main web service. One of the methods gets some report data, but in order to do that, web service (A) calls a method in web service (B). Depending what parameters I pass into "A"s method, it either works or fails. If I pass in a filter, the dataset is pretty small, when I don't pass in a filter obviously the dataset is very large. Additionally, if I run web service "A" in debug mode and point my desktop app to the local version (meanwhile B is on our production server), it works wether I filter the data or not. The error I get is a 502 Bad Gateway on production, and a 502 - Web server received an invalid response while acting as a gateway or proxy server.
We have a web farm with some ARR's, so I went into the web farm's ARR, and found "Proxy" settings and adjusted the timeout to 1200 seconds (whereas my app usually fails within 20-30 seconds) and I'm still receive this error. The HTTP version is in "Pass through" mode with the "keep alive" checkbox checked.
We have no issues using a windows service consuming a web service or anything like that, just when one web service consumes another web service.
Addition,
I'm not using any sessions in my web service methods, and I believe the webmethod I call in web service "B" does have a cacheduration value set of 5 minutes.
I'm scratching my head on this for my lack of knowledge of IIS 7, and many other things. If anyone has any ideas or can point me in the right direction I would certainly appreciate it.
I thought I'd come here and answer this question in case anyone else ran into the same issue. This issue was not server related at all. It was code related. In my code I had a datatable (c#), and was doing a datatable.select(....) where I would pass in a filter with many "OR"'s. Ex. Filter = 'x' OR 'y' OR 'z' etc etc. I had around 100 of these, which caused the datatable.select method to produce a stackoverflow exception. I changed the code to do an "IN (x,y,z)" and it works fine now. Hope this helps someone.
After installing VMware Server I get the following error when I try to access the VMware web-based server manager:
The VMware Infrastructure Web Service
at "http://localhost:8222/sdk" is not
responding
Go into the services manager and check that the 'VMware Host Agent' service is running. If not, then start it and then try browsing to the site again.
Vmware Hostd was not working for me either.
However, in trying to start the service it stopped automatically. Typically when this happens it is because there is an error in your config.xml.
C:\ProgramData\VMware\VMware Server\hostd\config.xml
In my case, checking the logs at:
C:\ProgramData\VMware\VMware Server
showed it erroring out after "Trying hostsvc".
Searching the config.xml for hostsvc showed references to several things, the first thing was the datastore. In checking my datastores.xml file:
C:\ProgramData\VMware\VMware Server\hostd\datastores.xml .
I found it full of all sorts of random characters instead of a properly formed XML document.
Renaming datastores.xml to datastorex.xml.bad allowed me to start the service. At which point I had to add back my datastores through the GUI.
Hopefully this will help someone else out. I did not find any other references in Google to this issue.
Try accessing via "http://localhost:8222" without the /sdk. You can also try the secure site via "https://localhost:8333".