been using PostSharp for 6 months now, just the Essentials part, no problems with local or TFS online builds, then this started to happen:
D:\a\1\s\ACME.Email.Publisher\ACME.Email.Publisher.csproj : error PS0242: License error. No valid license key has been installed. Please visit https://www.postsharp.net/purchase to acquire a license of PostSharp. To register a license key, use PostSharp Essentials or start the evaluation period, execute the program C:\ProgramData\PostSharp\5.0.44\bin.Release\PostSharp.Settings.UI.exe.
C:\Users\VssAdministrator\.nuget\packages\postsharp\5.0.44\build\PostSharp.targets(314,5): error : The process C:\ProgramData\PostSharp\5.0.44\bin.Release\postsharp-net40-x86-native.exe exited with code 11. [D:\a\1\s\ACME.Email.Publisher\ACME.Email.Publisher.csproj]
Build FAILED.
So...I've read the post sharp support page. Looks like their heuristics check for running in unattended mode - and thus not enforcing licensing -is now failing. Following their suggestions :
I've set up an environment variable like so: Environment.UserInteractive = false
I've printed the PID of the process running the build. It is 0 (although I don't have much control over that).
They suggest adding the license key to the build, I don't have one.
1-3 did not help so they suggest letting customer support know by using stack overflow and so here I am.
Related
Ugh....Microsoft have done something.
All our builds that have been kicked off in the last few hours (approx 10:00 GMT) are failing on our "Build Solution step" failing because of the following error (from the logs):
##[error]EXEC(0,0): Error : Error occurred during processing of input file 'XXX.XXX.dll' --> Method not found: 'System.ReadOnlySpan1 Microsoft.IO.Path.GetFileName(System.ReadOnlySpan1<Char>)'.
Does anyone have any ideas on this? Nothing in our codebase has changed.
If you need more information please let me know. Thanks
FYI, this seems to be caused by a recent update to MSBuild (https://github.com/dotnet/msbuild/pull/7680) that has updated the version of System.Memory.
It looks like the obfuscation tool you're using in your build pipeline is built against a previous version of System.Memory and now that the version provided by the MSBuild environment has changed, the obfuscation tool is broken. Most likely requires the obfuscation tool to be updated.
(PS. I'm just relaying the information that others have identified where other tools are having the same issue - see https://github.com/T4MVC/R4MVC/issues/172)
I am getting the following error along with a lot of others when trying to compile jobs on DataStage 11.7:
Error when checking composite operator: Subprocess command failed with exit status 256
I did an internet search of all possible solutions. Could not look at dsxchange as the site is down. Looked at all compiler options and they look the same as other projects with successful compilation.
IBM has a solution but it did not work for me:
https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.ds.trouble.ref.doc/topics/transformstage01.html
Any ideas?
There are 165 hits on DSXchange (it is not down).
Can you please verify your operating system and the values of the four environment variables that control your compiler and linker (APT_COMPILER, APT_COMPILEOPT, APT_LINKER and APT_LINKEROPT)? Please also verify the exact version of DataStage that you are running and the exact version of the compiler.
As noted in the Knowledge Center article, this error usually relates to the compiler being incompatible, the incorrect version, or having incorrect options.
I have C/C++ application and I am trying to run cov-build and getting a warning “ NO FILES EMITTED”. Can you please help me as we doing the POC on Coverity for static code analysis.
C:\Users\Master\bamboo-agent-home\xml-data\build-dir\DEC-L11PROJ-JOB1>cov-build --dir cov-int IarBuild.exe MainApplication\EWARM\L11_P4_uC1.ewp -build *
Coverity Build Capture (64-bit) version 2019.03 on Windows 10 Enterprise, 64-bit (build 18362)
Internal version numbers: 2c0f9c8cf4 p-pacific1-push-35439.872
IAR Command Line Build Utility V8.4.8.6680
Copyright 2002-2020 IAR Systems AB.
Total number of errors: 0
Total number of warnings: 0
[WARNING] No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
For more details, please look at:
C:/Users/Master/bamboo-agent-home/xml-data/build-dir/DEC-L11PROJ-JOB1/cov-int/build-log.txt
First, if you are involved in a pre-sales Proof of Concept (POC), then there should be a Coverity Sales Engineer assigned to help with the POC. That person's role includes providing instructions and information similar to what I'll offer below, as well as answering technical questions such as yours. There may have been a miscommunication somewhere. Get in contact with the Sales Engineer, as they will be able to help more reliably and completely than I can.
Now, what's going on? The primary purpose of cov-build is to watch the build process for invocations of compilers, and when one is found, compile the same code using the Coverity compiler (called cov-emit). But in order to recognize a compiler, cov-build needs to know its command line name, what kind of compiler it is, where its include files are stored, etc. This is accomplished by a helper tool called cov-configure that must be run before cov-build. If cov-configure has not been run, then no compiler invocations will be recognized, which appears to be the case for you, as indicated by "No files were emitted".
Synopsys has a page called CLI Integration Cheat sheet that gives these commands for use with IAR:
cov-configure --comptype iar:arm --compiler iccarm --template
cov-build --dir <intermediate directory> "c:\Program Files (x86)\IAR Systems\Embedded Workbench 6.5\common\bin\IarBuild.exe" sample_project.ewp -build Debug -log all
I can't personally vouch for these commands (I don't have IAR, nor access to the Coverity tools anymore; I'm a former employee), but something like that will be needed. Again, your assigned Sales Engineer should be able to help.
Finally, for new Coverity users, I recommend using the cov-wizard tool. cov-wizard is a graphical front-end to the command line tools, and has help text explaining the concepts and procedures, along with a convenient interface for performing them. There are several steps even after cov-build, and cov-wizard will walk you through all of them. Its final screen shows exactly what command lines it used in case you want to script them.
SignTool Error: An unexpected internal error has occurred. error MSB3482
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(3975,5): error MSB3482: An error occurred while signing: Failed to sign bin\Debug\app.publish\Halmanac.exe. SignTool Error: An unexpected internal error has occurred.
The error is the clickonce publish process for a winforms application in C# with clickonce deployment using a Code Signing Certificate from GoDaddy. The Certificate is good and current - expires 09-22-2020. If I remove the certificate (uncheck code signing), the error goes away and I can publish the exe. I want the certificate to prevent installation problems.
The application has been running for many years with minor changes each year. When I got the error, I restored a 6 months old copy that had been deployed with the certificate and I got the same error. Therefore, something has changed on the computer. I am running a current version of Windows 10.
How do I troubleshot this problem?
What do you recommend I do?
I don't know if this is your case, but in my case I was getting this error on an old project that I have not updated since 2019, I need to do some fixes and publish again. And this error shows with no changes to the project files (only code).
After reading this:
SignerSign() failed. (-2146869243/0x80096005)
Because of other Error with the exe sign, I revisited the code sign setting page and see that was using the timestamp server with the URL:
http://timestamp.comodoca.com/?td=sha256
I removed the /?td=256 part leaving it like:
http://timestamp.comodoca.com
And now the project compiles with no problem
I wanted to provide an answer to my own question. After a lot of research into all kinds of possible causes. I did use the signtool to sign the EXE manually. This atleast proved the signtool and CSC were working. In my last step, I looked at the compile parameters for 32bit and 64bit output exes. The software is one EXE and 2 DLLs. I made sure to examine every parameter involved in making the EXE. After a number of changes/fixes/tweaking, the software published a Clickonce EXE. I installed the EXE from the Internet and everything worked. I do not know what fixed the problem, but the error is gone. In my opinion, there was a conflict in parameters between the EXE and DLLs. Robert Neal 07-15-2020
I ask this Question because it is Moles specific.
Running VS2010 on Windows 7 64bit the VsHost of moles stays in the task manager, causing this message:
Unable to copy file
The process cannot access the file because it is being used by another process
Solution: Kill the Process Microsoft.Moles.VsHost.x86.exe in the Task-Manager
To do this very often is very very annoying. I read in the msdn social forum that this issue shall be fixe sometime (i recall the post was from 2010 but cant find the post).
This happens nearly every time I stop the Debugging of the Test or if there is an Error while Debugging.
Anything new about this Issue?
I very much hope that Moles will be a standard part of Visual Studio someday, because I like this Typemocking very much!