I'm getting this list of errors*(C:\a\src\Allegro Web.nuget\nuget.targets (88): Unable to find version '2.0.1.0' of package...*) all of a sudden after doing a normal commit, please find below, however i didnt change any nuget specific configuration recently.
It was an intermittent issue with Nuget which is fixed now.
More details on that here: https://twitter.com/nuget
Related
I got a HPCC community version 8.0.0.1 installation running. Whenever I try to add a new FilScope trhoug ECL Watch nothing happens. It simply doesn't create it.
I got some version 6.4 clusters running and this problem doesn't happen. Works fine there.
When I try to delete Scopes created on ver 6 through version 8 I got the error "BaseDN not specified". On the logs I see the same thing.
I am not missing any basedn configuration of the already in place basedn fields on environment.xml.
Thanks for posting this question. I just did some research, and found that this problem has been reported and is fixed in a newer release. Please try build 8.6.42 or newer.
FYI, it was fixed with this issue
https://track.hpccsystems.com/browse/HPCC-27892
Russ Whitehead
Not sure what details I should be providing to be completely honest, other than I googled and searched for this solution and I deleted everything and retried and didnt work out, I downloaded all the files needed, I added application settings and it added an error for me telling me that I need to install or update Microsoft.WindowsDesktop.App, version 3.1.0, which I have installed and already existed anyway
I tried going to application event logs on Azure portal, there was 3 errors first this one which some people suggested going to web.config and changing it to Module not v2, and I dont see any web.config file in my mvc project
2nd error which I already talked about but its just not working, so I assume somehow its not seeing it??
3rd error Also this I am not quite sure what to do with it.
Lastly, as I said I am not sure what information I should provide, I dont have much time and I was asked to publish it on azure there was no problems and seemed easy but errors popped up and nothing on the internet fixed my issues, you can comment and I will add any required data to fix this.
Thanks in advance
I installed each and every package in the dotnet folder to make sure everything is right and everytime it recognized there is a file already and asked me if I want to repair I said yes but that didnt help
I checked my .json file if it had any errors like some people suggested
checked if Azure portal specified that I am using ASP.NET 3.1core which it did
~~I used search for "stdoutLogFile" to check if I can find it anywhere on my solution since I cant find my web.config but I there was no result~~
I found out that I can add the web.config and make changes to it, and I did so but there was no result for it, still same error (yes I change the publish profile and republish to make sure it took the changes)
[enter image description here][1]
[1]: https://i.stack.imgur.com/rgiVi.png I got these errors when I opened the profile.arm.json folder under the server dependency folder
Since last week, my SSIS packages running in Azure Data Factory (v2) are failing one by one. They haven't changed though. All the packages are failing with the same series of errors, as shown below.
The packages are running perfectly in Visual Studio, but when I deploy them to Data Factory, I got these messages.
Any thoughts on where to look?
I've tried to recompiled the script components, to redeploy the whole project. I've also tried to copy the C# code into a new component, unfortunately results in the same issue.
So I was driven kind of crazy by this, had the exact same problem, and was troubleshooting with the assistance of Innovative Architects, a group near Atlanta. And we discovered that LITERALLY TODAY Microsoft released an updated version that fixes this exact problem. So apparently it was a bug that they fixed.
See here for the fix.
I have API Connect installed with mongodb connector over a remote server.
When I access the IBM API Connect through browser, all is fine, but when I go to DataSources where my DB is, and try to hit Update Schema button as shown in the image, an error occurs showing this:
Cannot GET /apim/dataSources/partials/dataSourceMigrate.html
P.S. I gave full permission for my project directory (/var/www/) with full ownership for www-data group and still the same.
Anyhelp would be appreciated.
FINALLY AND AFTER 2 MONTHS OF WAITING, I've got an answer from IBM Bluemix Support and sorry to bring the bad news, which is the following:
Hi Ghassan,
Thanks for sending the additional files. I checked with our development team and they found a bug in the code.
The fix will be available in a future release of the apic command line, but I don't have a date for it yet.
I will further discuss the plans to release this fix and will update you as soon as possible.
IBM Bluemix Developer Support and Enablement Team
A fix has been provided for this issue in iFix versions of 5.0.3.0, 5.0.4.0 as well as newer versions of API Connect. If you are still experiencing this issue, please update to a later version that includes the fix.
I am trying to set up an internal nuget feed for my company. I have built the site and deployed it to IIS server. I can install from the site itf I manually add packages to it but I cannot push to it from the command line. When I try to I get prompted for credential (none work) then get an error that says "Cannot access a closed Stream." I have been to NuGet and read everything they propose but none of it works. I am thinking this is a server setting but I have no idea which one. Has anyone encountered this that can share the solution?
Solved this issue by removing WebDAV and adding PUT to the web.config authorization
I just added a comment to the Github issue tracker for a similar (probably identical) problem raised there:
https://github.com/NuGet/NuGetGallery/issues/487
This is probably a result of WebDAV being installed in IIS - it seems to interfere with the settings required for NuGet Gallery. We certainly saw a similar issue with 405 errors, and uninstalling the WebDAV module fixed the problem.