Error installing Sql Server sink - Semantic logging - semantics

I'm trying to install Semantic logging Sql Server sink into my application but each attempt so far failed. The error I'm getting is (in CMD mode):
Attempting to resolve dependency 'EnterpriseLibrary.SemanticLogging (≥ 1.0)'.
Attempting to resolve dependency 'Newtonsoft.Json (≥ 4.5)'.
Attempting to resolve dependency 'EnterpriseLibrary.TransientFaultHandling.Data (≥ 6.0)'.
Attempting to resolve dependency 'EnterpriseLibrary.TransientFaultHandling (≥ 6.0)'.
Installing 'EnterpriseLibrary.TransientFaultHandling 6.0.1304.0'.
You are downloading EnterpriseLibrary.TransientFaultHandling from Microsoft, the license agreement to which is available at http://www.opensource.org/licenses/ms-pl. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Install failed. Rolling back...
install-package : The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
At line:1 char:1
+ install-package
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], PathTooLongException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
Tried both UI and command prompt installations still no luck. Any help would be appreciated very much.

Had a similar problem. You might try to move just this single package to a shorter directory, e.g. C:\Packages. Otherwise move your whole project path (e.g. C:\users\yourname\documents...) to a short path like c:\MyProjects.

Related

compile errors after upgrading to latest CRA

I just updated to latest create-react-app (web pack 5). And am now getting the following errors (I'm just showing the first 2 errors here). Any help explaining what this error means and how to fix it would be greatly appreciated. I don't think the problem is with react-pdf because I created a new create-react-app project that uses that package and there's no problem.
{
Compiled with problems:X
ERROR in ./node_modules/react-pdf/node_modules/#babel/runtime/helpers/esm/inherits.js 1:0-46
Module not found: Error: Can't resolve './setPrototypeOf' in '/Users/bob/dev/workbox-web/node_modules/react-pdf/node_modules/#babel/runtime/helpers/esm'
Did you mean 'setPrototypeOf.js'?
BREAKING CHANGE: The request './setPrototypeOf' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/react-pdf/node_modules/#babel/runtime/helpers/esm/objectWithoutProperties.js 1:0-74
Module not found: Error: Can't resolve './objectWithoutPropertiesLoose' in '/Users/bob/dev/workbox-web/node_modules/react-pdf/node_modules/#babel/runtime/helpers/esm'
Did you mean 'objectWithoutPropertiesLoose.js'?
BREAKING CHANGE: The request './objectWithoutPropertiesLoose' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
}
Somehow I was accessing a wrong version of babel after CRA upgrade to 5. Deleting node_modules and re-installing was not enough. I needed to delete node_modules and yarn.lock and then yarn install - and then all was ok.

Unable to find package 'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'

I'm using swagger, but I have this problem according to the documentation. The nuget package has not been downloaded successfully. What should I do?
This is the error message:
Severity Code Description Project File Line Suppression State Error
The feed'nuget.org [https://api.nuget.org/v3/index.json]' lists
package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3' but multiple attempts
to download the nupkg have failed. The feed is either invalid or
required packages were removed while the current operation was in
progress. Verify the package exists on the feed and try again. Unable
to find package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'.
Update:
I try to use the command:Install-Package Swashbuckle.AspNetCore -Version 6.2.3
Error:
Maybe a problem on your internet connection? Package seems exist (https://www.nuget.org/packages/Swashbuckle.AspNetCore.SwaggerUI/6.2.3).

cannot use add-Migration in .net core 2.1 project using visual studio for mac

I am using Visual Studio for Mac and have .NET Core 2.1 project. I have an issue when using any migration command like "Add-Migration", namely the following error occurs:
**Add-Migration : The term ‘Add-Migration’ is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Add-Migration DBUpdates -Context applicationdbcontext
+ ~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Add-Migration:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException**
Any clue what the cause of this could be?
This error indicates that one package is missing.
Install package Microsoft.EntityFrameworkCore.Tools from nuget. Then reopen the visual studio.
You might be missing the nuget package, if thats not the case also double check you have the powershell interface in Visual Studio pointing at the correct project (You want the one where your DbContext object exists and is defined)

Publishing #progress/kendo-ui to nexus 3..5.1 npm pkg repository

We've migrated from Nexus 3.01.01 to 3.5.1-02. In the process we had to migrate internally published npms. One of those is the kendo-ui (commercial one) from Telerik/Progress. We have downloaded the licensed copy from Telerik and publishing it to our local nexus for consumption by our developers.
However the publishing fails with an error during payload parsing. I can publish the same tar without an issue to the older (3.01.01) nexus, so the tar/payload it self is OK.
The error seem to be at the point of trying to parse the npm payload. I can also publish a demo/simple npm (both scoped and non-scoped) without an issue. Spend the whole day trying to figure this out with no luck - appreciate any pointers or advice.
2017-09-06 18:49:09,160+0800 WARN [qtp762281666-4116] MIDALLE
org.sonatype.nexus.repository.httpbridge.internal.ViewServlet -
Failure servicing: PUT /repository/npm-hosted/#progress%2fkendo-ui
java.lang.IllegalStateException: Unexpected token VALUE_NULL at
[Source: java.io.InputStreamReader#1ebad5c7; line: 1, column: 896] at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:150)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseObject(NpmPublishParser.java:174)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:136)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseObject(NpmPublishParser.java:174)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:136)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parsePackageRoot(NpmPublishParser.java:123)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parse(NpmPublishParser.java:98)
at
com.sonatype.nexus.repository.npm.internal.NpmRequestParser.parseNpmPublish(NpmRequestParser.java:81)
at
com.sonatype.nexus.repository.npm.internal.NpmRequestParser.parsePublish(NpmRequestParser.java:60)
at
com.sonatype.nexus.repository.npm.internal.NpmHostedFacetImpl.putPackage(NpmHostedFacetImpl.java:85)
at
com.sonatype.nexus.repository.npm.internal.NpmHandlers$3.handle(NpmHandlers.java:172)
at
org.sonatype.nexus.repository.view.Context.proceed(Context.java:80)
Here's the gist for the full error from the nexus log.
This issue was resolved in scope of https://issues.sonatype.org/browse/NEXUS-14385
Fix Version/s:
3.6.1
There was a problem with parsing null values in package.json
I got this to work however I'm still trying to figure out the impact of the change. Please be cautious if you apply the same 'hack' to get this to work. I had to do this, because there was several other project teams that was getting affected.
In a nutshell I had to strip out few keys from the package.json of the kendo-ui package. My analysis is that these settings makes npm issue a network call that fails in our constraint environment.
The package.json keys that I removed are as follows.
First section
"_resolved": "https://registry.npm.telerik.com/#progress%2fkendo-ui/-/kendo-ui-2017.2.621.tgz",
"_shasum": "09a652ead21700716dd5a50f9e86e9bffcea640e",
"_shrinkwrap": null,
Second section
"dist": {
"shasum": "09a652ead21700716dd5a50f9e86e9bffcea640e",
"tarball": "http://registry.npm.telerik.com/#progress%2fkendo-ui/-/kendo-ui-2017.2.621.tgz"
},
I'd really appreciate if someone who know more about npm and npm definitions can inform the purpose of these settings in the package.json and potential impacts of removing them.

How to build apache HCatalog 0.5.0?

Its been almost 3 hours and I'm not able to build this. Please can anybody provide the steps. All the documents suggest to use hcatalog-src-0.5.0-incuvating.tar.gz but this is not available anywhere on internet (ad far as I've searched). Then I downloaded the branch 0.5.0 but as per the documentation
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.2.0/ds_HCatalog/install.pdf
of version 0.5.0 you have to build l=using command
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home tar
Now the problem is that the build.xml do not have a target named 'tar'. So I just browsed the build.xml and tried the same command using target as 'package'
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home package
but then its showing me error.
BUILD FAILED
C:\Users\admnilesh\Desktop\hcatalog-branch-0.5\build.xml:71: The following error
occurred while executing this line:
C:\Users\nilesh\Desktop\hcatalog-branch-0.5\build-support\ant\deploy.xml:67:
Unable to resolve artifact: Unable to get dependency information: Unable to read
the metadata file for artifact 'com.sun.jersey:jersey-core:jar': Cannot find pa
rent: net.java:jvnet-parent for project: com.sun.jersey:jersey-project:pom:1.9.1
for project com.sun.jersey:jersey-project:pom:1.9.1
com.sun.jersey:jersey-core:jar:1.9.1
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2),
glassfish-repository (http://maven.glassfish.org/content/groups/glassfish),
datanucleus (http://www.datanucleus.org/downloads/maven2)
Path to dependency:
1) org.apache.hcatalog:webhcat:jar:0.5.0-SNAPSHOT
Please help me out.
We've been having the same trouble and discussing it over at the hcatalog-user mailing list for the last couple of days. You can have a look at https://issues.apache.org/jira/browse/HCATALOG-601 to see what's being done about this problem.
Quick summary though : Jersey 1.9 depended on a glassfish maven repo, which no longer exists. Bump your jersey dep version from 1.9 to 1.14 and you should be able to build.
Edit : One more thing - we're still going through the release process to release the 0.5.0 incubating candidate, the latest candidates are being put up currently on http://people.apache.org/~travis/ . We should see a public release in a couple of days. In the meanwhile, I suggest poking over at our hcatalog-user mailing list : http://incubator.apache.org/hcatalog/mailing_lists.html
I got the same error while giving target "tar". On specifying the target as "package", the build proceeds ahead but fails with following error:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies] ----------
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies]
[artifact:dependencies]
[artifact:dependencies] Path to dependency:
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-pig-adapter:jar:0.5.0- incubating
[artifact:dependencies] 2) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies] ----------
This issue got resolved by specifying project.version as "0.5.0-incubating" instead of "0.5.0" in build command line. The reason for error is that build installs hcatalog-core artifact as hcatalog-core-0.5.0-incubating.jar. However because of wrong project.version, the dependent projects were instead searching for hcatalog-core-0.5.0.jar.
Build succeeded with:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0-incubating -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package