While trying to add the host instances to the WCF Custom Adapter as a send handler I am getting the below error messages.
I tried resetting my password and restarted and that didn't work. Also, I tried to change the domain of my machine and bring it back to the original domain but I was not able to do it because of access issues.
Can someone please suggest why this error is occurring at this stage and how can I resolve it?
The above issue is resolved now. The actual problem was with the workstation/Computer name. At the time of BizTalk configuration I had only given the workstation/computer name, but instead we should give FQDN (fully qualified domain name) like workstation1.xyzcorp.net while configuring biztalk. This resolved my issue.
Thanks.
Related
I have a Windows 2012 R2 server and I managed to install the SonarQube 5.4 server as a Windows Service. I also set up a user so the service can actually start without the infamous "It started then stopped" error a lot of people seem to get. Before installing the server as a windows service, I checked that it worked using StartSonar.bat and it did work just fine, so I was confident when I made it into a service.
But when I try to access http://localhost:9000 there is nothing there, and it appears that shortly after starting the service it stops without any message at all. I can't tell if this is because I try to access the site (which gives me ERR_EMPTY_RESPONSEin Google Chrome) or if it just closes down after a short while.
Anyone got any insight?
I'm a beginner. I came across the same issue and fixed it.
Ensure that the database is running.
My log file (located at sonarqube_home_dir/logs/sonar.log) included the following statement.
Caused by: org.h2.jdbc.JdbcSQLException: Wrong user name or password [28000-176]
Since I'm using the default database, I commented below lines
#sonar.jdbc.username=***
#sonar.jdbc.password=***
at sonarqube_home_dir/conf/sonar.properties.
This must happen due to many reasons like connection problems, permission problems so First, you have to see the logs. /sonarqube-7.6/logs$ tailf sonar.log. then you can find the reason. Once I had the same problem so I did like that. my error is something Directory does not exist: lib/jdbc/mysql
org.sonar.process.MessageException: Directory does not exist: lib/jdbc/mysql reason is I uninstall MySQL and remove all folders name contains "MySQL".
just check whether port 9001 already in used, stop it if already in used.
I had created a web application and committed the code in CVS. The web application is working good in my machine. When i tried to import the same code in another machine i am getting 404 error. I tried importing the code via ftp from my machine to another machine and also checking out the code from CVS. But still i get 404 error.
I also noticed that there is no error that had been captured in the console or in the application's log. Could someone help me in how to proceed further in identifying the issue. Please let me know if i need to post any further details regarding the issue.
I notice this issue to be in the Websphere server. I tried hosting the application in different machine and found that in few machine the same code is working good and some it is not. Is there any way to compare the server configuration?
In the WAS server 6.1 i added the below value in the web container and the application worked fine.
Steps:
In the server admin console, click on Application Server--> --> Web container--> custom properties.
Add the name as com.ibm.ws.webcontainer.invokefilterscompatibility and value as true.
Thank you all for the response.
I am facing an issue on accessing TFS portal using
http://ServerName:8080/tfs
it's showing "Page cannot be displayed"...! It's happening only in the TFS server. Portal is working fine when I access it from other machines.
http://localhost:8080/tfs is working perfectly in the server.
Please help me to resolve this.
Issue has been resolved and the steps shown below.
Mapping of IP address to host name was missing in the host file. An entry has been created in the "host" file under "C:\windows\System32\drivers\etc".
The loopback check functionality has been disabled by creating registry key under the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck and assigned the value “1”.
Restarted the machine.
Thank you very much for the replies.
I'm setting up a new .NET MVC project and want to use my local ADFS for managing users. I know the IP address of the machine my ADFS is running on and have tried using that for the 'On-Premises Authority' URL, but I got an message stating that it was incorrect.
Is there a command I can run to find the address/url that I should be using for this field?
For reference, this is the menu box I'm talking about:
You insert the metadata address of your ADFS e.g.
https://some-server/federationmetadata/2007-06/federationmetadata.xml
This must be provided by your IT-Team.
Usually it is:
https://YOUR-ADFS-SERVER/FederationMetadata/2007-06/FederationMetadata.xml
I am facing a strange issue with azure -
After uploading a new version of my app about an hour back, the public facing url is throwing a runtime error. However the app works fine when I access it through the azure internal domain -- app.cloudapp.net.
Before upgrading it was working fine.
I have rechecked the cname records with my hosting provider (bluehost) but I cannot find any problem. Even otherwise, the problem seems like an ASP.net issue (due to the typical error page rendered) but something that just does not make sense.
Anyone has any ideas as to what I can do?
EDIT: This started working just as mysteriously as it had stopped - I have no clue whether it is due to DNS propagation delay (although in that case it should not have thrown an error page like described above). However if someone knows why this might happen, I will still appreciate it.
There is a DNS service available for Windows Azure called "DNS Azure" that changes your cloudapp's IP address automatically. See dnsazure.com
This solutions helps to avoid the CNAME record because the A record is kept up-to-date.