Hi We are running Azure Devops Server 2020 update 1 patch 4. We want to use the Search functionality On a dedicated server). Im following the steps on this site: https://learn.microsoft.com/en-us/azure/devops/project/search/install-configure-search?view=azure-devops-2020#secure-search.
I'm getting stuck at the Readiness checks with an error in the log:
[Error #14:31:33.683] search plugin with version: '6.2.4.22' is not compatible, supported search plugin version: 6.2.4.18
[Info #14:31:33.683] Node returned: Error
[Error #14:31:33.683] Elasticsearch plugin: 'AlmSearchPlugin' with version: '6.2.4.22' is not supported. Ensure that your remote Search server has been updated to the latest version prior to configuring Search.
[Info #14:31:33.683] Completed Service Not Installed: Error
When going to through the details of the patch 4 I read that you should check the registry value and set the Version to 5.4.1. For me after the installation it was set to 6.2.4.1.
I gave it a try by setting it to 5.4.1 and run the command:
.\Configure-TFSSearch.ps1 -Operation update -verbose
Unfortunately after this the value was again set to 6.2.4.1 and also the readiness checks gave the same results.
This error was also reported on the blog-page about this patch. But there was not really an answer, but tweaking some files coming from the installation folder (see comment Edwin Siebes; feb 1st). Is this really the solution? Or did I miss something?
After contact with Microsoft support I got a new dll: Microsoft.TeamFoundation.Admin.dll which fixed the problem.
This was a private patch they said they going to make it public.
Related
I have wildfly 10 and installed APIMAN 1.5.1.APIMAN. Organization/API creation is done and while publishing the API, I'm getting below error
io.apiman.manager.api.rest.contract.exceptions.ActionException: Failed to publish API.
I too had this issue, in my case problem was with the ElasticSearch.
apiman.es.host defined in standalone/configuration/apiman.properties was not working.
Check host and port that are mentioned are open/working.
I have installed ICP CE 2.1.0 on a google cloud VM and the installation has gone well-no errors in installation process. When accessing the GUI I am able to see deployments and services but as soon as I access any part of the Catalog I get a blank white page with the text:
{"statusCode":401,"details":"Unexpected response code 401 from request:\nGET https://xx.xxx.xxx.xx:8443/console/api/v1/header?serviceId=catalog-ui&dev=false&accessUrl=https%3A%2F%2Fxx.xxx.xxx.xx%3A8443* ...... }
I have tried killing the individual pods but I get same error. When looking a the pod logs for the catalog-ui I have error 500 messages.
Has anyone experienced this or can tell my why this is the case? Understand that a cloud VM is not the best use case maybe but it should work?
Can you confirm the version level of ICP? Your post mentioned "ICP CE 2.1.0" but if you can check the user icon (top right corner) and click About, we should be able to see the full version details.
Reason for asking is that, at the 2100 level there was an intermittent catalog issue just like you describe. Generally it was caused by resource constraints on the k8s.
Details for ICP 2103, which is the latest available release:
https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.3/getting_started/whats_new.html
We got following issue when we test SonarQube 5.2. Perforce plugin starts to behave incorrectly. It prints error in log:
[07:30:30]W: [] [ERROR] Perforce password (P4PASSWD) invalid or unset.
[07:30:30] : [] [DEBUG] Perforce password (P4PASSWD) invalid or unset.
Even if I set -X for Maven I did not get more details why it prints this error.
Only difference it that it uses SonarQube 5.2. On SonarQube 5.1.2 it works fine. Also it looks like upload passes and no report is shows on SonarQube server UI.
Only message I see on server log is:
12:32:31 ERROR web[o.s.s.c.t.CeWorkerRunnableImpl] Executed task | project=<prjkey>
| id=AVFYYUYrsGEyA8a-XeTJ | time=2231ms
again without any details even if I set DEBUG log level.
Secondary problem is that I tried to register to JIRA for SonarQube but I am not able to create new issue. I can only view existing issues. So only option is to ask here.
P4PASSWD is a variable which is supposed to contains the password of the current user.
Check if you have entered it somewhere in the plugin configuration. You can also try to set it up manually by calling p4 set P4PASSWD=XXX. This is not the cleanest solution but it might be a temporary workaround.
My migration fails on the user mapping task with the following error :
OpsHub-014371: Could not instantiate metadata implementation for For User List | TFS Source 1412109029732 ALM TFS 1412109029738, due to (301)Moved Permanently
I am running on v1.0.1.006.
Thanks for help
If the machine that you are using the utility on behind a proxy then this issue will come, new version will be available on first week of November.
Last night, at home, where I do not work with a proxy, updated a NuGet repository using NuGetPowerTools / Enable-PackageRestore.
Worked great.
Came into the office, where i am working with the same Repository under the following conditions:
in a VMWare based VM,
using Bridged Networking,
Reinstalled NuGet today, restarted (to be sure I have latest version)
runnning under an account in a DEV Domain (ie, DEV\Me)
Accessing the outer world via a Proxy that requires a corp Domain Account (ie, CORP\Me)
Ie 9's Configuration/Internet Options/Connection is setup as:
Use Proxy:
Address: yadayada1
Port: 80
Bypass proxy for local addresses
Automatically detect Settings
Above settings are correct in as much that I can access the web via IE9, Chrome, etc.
NOTE: Can list and download Nuget packages...it's just the new Build process that can't.
As per suggestion on the web I have looked at DevEnv.exe.config and have the following settings:
-<system.net><settings><ipv6 enabled="true" /></settings></system.net>
I also tried with these settings as
<system.net><defaultProxy useDefaultCredentials="true"><proxy autoDetect="True" usesystemdefault="True" /></defaultProxy></system.net>
so that DevEnv.exe falls back for to same connection settings that IE 9 is using. Didn't do it.
What I get for all this is:
------ Build started: Project: XAct.Core, Configuration: Debug Any CPU ------
Please provide proxy credentials:
UserName: Password:
C:_Workspaces\XAct\CS.FF.XAct.Lib2.nuget\NuGet.targets(43,9): error : Cannot read keys > when either application does not have a console or when console input has been redirected > from a file. Try Console.Read.
C:_Workspaces\XAct\CS.FF.XAct.Lib2.nuget\NuGet.targets(43,9): error MSB3073: The
command ""C:_Workspaces\XAct\CS.FF.XAct.Lib2.nuget\nuget.exe" install
"C:_Workspaces\XAct\CS.FF.XAct.Lib2\XAct.Core\XAct.Core\packages.config" -source "" -o
"C:_Workspaces\XAct\CS.FF.XAct.Lib2\packages"" exited with code 1.
Found (but unfortunately lost again) a thread somewhere on the net where I saw NuGet developers thrashing it out -- referring to downloading the latest build from their TeamCity (which I could not access/join) -- but the thread did not clearly say Eureka! at the bottom.
Thanks.
Reiterating what Sky and Pranav mentioned - this issue seems to be fixed in NuGet 1.7 - see http://nuget.codeplex.com/workitem/1655:
pranavkm wrote Jan 31 at 8:17 PM
Fixed in changeset 6c156e0dc214