I wrote a basic micro service. Both micro new and make proto work fine. All dependencies installed. micro server also running, BUT, when I do cd myservice and then micro run . ( I have local env by the way) this errors shows:
Rpc error: code = Unknown desc = Error writing source to blob store: open C:\Windows\micro\store\blob.db: El sistema no puede encontrar la ruta especificada(System can not find the specified route).
I have the micro binaries in my go installfolder/bin this way
C:\Program Files\Go\bin
λ ls
bin
go.exe
gofmt.exe
include
micro.exe
I dont know what I am missing but go mod tidy and go mod vendor execute well. Anyway, I have the feeling that running micro in windows is a headache.
Related
I'm trying to deploy a monolith JHipster demo on AWS using AWS-containers
c:\jhipster\demo>jhipster aws-containers
..
🔧🛠️ AWS configuring
√ ECR Auth token has been retrieved.
Run-async async() called outside a valid run-async context, callback will be ignored.
AWS default
Warning demo is using a cache provider, scaling will not be available. Refer to an AWS native scaling service.
force ..\..\Users\demo\.yo-rc-global.json
identical pom.xml
identical src\main\java\com\demo\bootstrap\AwsSSMConfiguration.java
identical src\main\resources\META-INF\spring.factories
force .yo-rc.json
identical src\main\resources\config\bootstrap-aws.yml
identical base.template.yml
identical demo.template.yml
Run-async wrapped function (sync) returned a promise but async() callback must be executed to resolve.
× ".." no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
× The Docker image build failed. Error: Command failed: ../demo/./mvnw -ntp -Pprod verify jib:dockerBuild
".." no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
I'm using JHipster 6.10.5 on windows 10.
The output is partially on spanish, the translation is:
'..' is not recognized as an internal or external command
it's a environment issue caused by windows 10.
I see the same error at
https://github.com/jhipster/generator-jhipster/issues/8366#issuecomment-489498566
Also looks like a windows machine.
Is trying to execute
../demo/./mvnw -ntp -Pprod verify jib:dockerBuild
that not is a valid command on windows system.
Any idea about how fix it?
I'm using Salt to install a windows only software called Alteryx.
I've created an /srv/salt/alteryx/alteryx.sls as follows:
alteryx:
'2018.3.4':
installer: 'salt://win/repo/alteryx/Rinstaller_2018.3.4.51585.exe'
full_name: Alteryx Designer 2018.3.4
reboot: False
installer_flags: '/S /l="C:\temp\alteryxInstall.log'
My saltstatck file is in /srv/salt/alteryx/init.sls is simply
alteryx:
- pkg.installed
When I try to apply this state (salt -G 'roles:alteryx' state.apply) I get the following error:
hostname
Data failed to compile:
--------
ID alteryx in SLS alteryx is not a dictionary
I've tried placing the alteryx file in /srv/win/repo-ng/salt-winrep-ng/. But I get the same error.
What else do I need to do to get this package installed?
First of, if you have a look at sample package definition sls file, there is no installer_flags argument. It should be install_flags instead.
Second, Salt doesn't distribute SLS file for windows packages itself, you need to sync them across manually every time a change is made.
From your Saltmaster run,
salt-run winrepo.update_git_repos
Run pkg.refresh_db on each of your Windows minions to synchronize the package repository.
salt -G 'os:windows' pkg.refresh_db
Please have a read at this as well.
I am trying to register the Windows 10 Edge package with Windows Server 2016. I have successfully installed the store thanks to a forum I found and it opens but remains untested. I am trying to do the same with Edge. I've copied the app package from the installer iso to C:\Windows\systemapps and ran the power shell script:
Add-AppxPackage -register "C:\windows\systemapps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Appxmanifest.xml" -DisableDevelopmentMode
And get the following error:
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor.
(Exception from HRESULT: 0x80073CF9)
Rejecting a request to register from Appxmanifest.xml because the manifest is not in the package root.
NOTE: For additional information, look for [ActivityId] a80e1223-2787-0000-dc3e-12a98727d301 in the Event Log or use
the command line Get-AppxLog -ActivityID a80e1223-2787-0000-dc3e-12a98727d301
At line:1 char:1
+ Add-AppxPackage -register "C:\windows\systemapps\Microsoft.MicrosoftE ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (C:\windows\syst...ppxmanifest.xml:String) [Add-AppxPackage], IOException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand
I've verified the manifest is in the package root so other than that I can't figure out what it means. Can someone help me understand what it's looking for?
Reference for store install: http://virtualcustoms.net/showthread.php/72904-Install-Microsoft-Store-and-Apps-on-Windows-10-LTSB-2016
I was just trying to do the same thing and I have found if I copy the app to C:\Program Files\WindowsApps then it installs without complaining about not being in the root and then the Edge icon also appears on the start menu.
The command to run is:
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppxManifest.xml"
Whilst this allows the app to install and I am able to launch it from the start menu it closes after about 2 seconds and looking in the log (Application and Service Logs\Microsoft\Windows\Apps\Microsoft-Windows-TWinUI/Operational it shows this error so it looks like there is still something else that needs to be done to get this working:
ActivateApplicationForContractByAppIdAsUserWithHost of the app Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge for the Windows.Launch contract failed with The app didn't start..
Robin
I found it difficult to add to the win apps folder but figured out as long as the location of the apps you want to add are located in a folder named C:\Program Files\WindowsApps* it will work. I use a folder named “WindowsApps-Import” in the programs folder, works well!
One answer suggests adding the -DisableDevelopmentMode flag to the command you've ran, which works, but leaves an important point out.
Once the app installs, it won't run and crashes soon after. This is because the ALL APPLICATION PACKAGES group doesn't have access to the folder of the app. Giving ALL APPLICATION PACKAGES full control of the app folder will allow it to run.
Move the folder inside: "C:\Users$USERNAME\AppData\Local\Packages" then it works. Obv developer mode on windows needs to be ON.
for eg:
Add-AppxPackage -Register "C:\Users\Amit\AppData\Local\Packages\WsaPackage_1.7.32815.0_x64_Release-Nightly\AppxManifest.xml"
I am using Marmalade to build a PlayBook app, but I think my question applies to PlayBook apps in general. I have successfully created a debugtoken.bar file and have installed it on my device. When I go to try to install a built application.bar file on the device, I get:
[execute] "blackberry-deploy.bat -device 192.168.1.114 -password ******* -installApp -package deployments\default\playbook\release\Quote Unquote.bar"
Info: Sending request: Install
Info: Action: Install
Info: File size: 6400334
Info: Installing ...
Info: Processing 6400334 bytes
actual_dname::
actual_id::
actual_version::
result::failure 881 required signatures missing (RDK, AUTHOR)
ERROR: error running blackberry-deploy
***ERROR***
Note that this is the Marmalade deploy tool running the standard PlayBook installer.
What I don't understand is: I thought the point of using a debugtoken.bar file was that you could install unsigned apps. I have in fact successfully deployed these unsigned apps using the Marmalade deploy tool just like this. But I was having problems signing the app for distribution, so I went back and did everything from scratch, requested new code signing keys from RIM, made a new debugtoken.bar file and installed it, etc. And now I'm worse off than I was before because I can't even install to the device now.
So again: My understanding is that the point of debugtoken.bar was to be able to deploy to the device before actually signing the application.bar for distribution. So what does this error message even mean?
To answer my own question:
For deploying a "debug" build to a device, it's critical to have
Application-Development-Mode: true
in the MANIFEST.MF within the .bar file.
A stupid mistake, but I'll leave this up in case it helps anyone...
Taking a look to the QNX deployment plugin "C:\Marmalade\6.1\s3e\deploy\plugins\qnx\qnx.py" I found that 'FOR DEVELOPMENT' option is false if the 'playbook_keystore' is given so I just cleared the signing section on the Marmalade System Deployment Tool and it is not longer trying to sign it
I've just get a new machine and try to checkout, build and launch my program.
When hitting "launch in debug" button, I have this error message poping up from MS VS:
Unable to start program 'xx'. This
application has failed to start
because the application configuration
is incorrect. Reviex the manifest file
for possible errors. Reinstalling the
application may fix this problem. For
more details , please see the
application event log.
Have a look into the application event log:
Type de l'événement : Erreur Source de
l'événement : SideBySide Catégorie de
l'événement : Aucun ID de l'événement
: 59 Date : 24/08/2009 Heure
: 16:10:03 Utilisateur : N/A
Ordinateur : XXXXXXXX Description :
Resolve Partial Assembly a échoué pour
Microsoft.VC80.DebugCRT. Message
d'erreur de référence : L'assemblage
référencé n'est pas installé sur votre
système. .
Pour plus d'informations, consultez le
centre Aide et support à l'adresse
http://go.microsoft.com/fwlink/events.asp.
Ok , the text is in french, but it roughly tells that that resolving the "partial assembly" didn't work for "Microsoft.VC80.DebugCRT". It conludes so that this assemlby is not installed on my machine.
Having a look into the C:\windows\system32 folders, I see no mscvrt80d.dll file. (Huu .. Is it this one I should expect?). MS visual studio 8.0 is freshly installed by admin system though.
Did you ever have that issue before ? And how did you fix that ?
It is not the neatest solution, but in addition to shared SxS installs of the C-runtime - which incidentally are installed to a folder: c:\windows\winsxs - its completely legitimate to perform what is called a "private side-by-side" install - which for debug builds will be most convenient.
Simply go to your folder: C:\Program Files\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist\x86, and copy the appropriate folder into the deployment folder of your debug build:
So, if your app is installed in C:\Test\MyApp, you would now have a folder called C:\Test\MyApp\Microsoft.VC80.DebugCRT
(You can also copy the foles from the assembly straight into your app folder, but I find that messy).
Actually CRT was not the issue here. What caused the problem was that another lib I used was compiled by a co-worker on his machine and sent to me through shared directory. Therefore the recipient folder for the DLL was not the same as it was on the original machine from my coleague. I guess the issue is because the manifest files expect it to be the same(?), or does it expect to find the source code at a specified path (?).
Anyway, re-compiling the lib in question from scratch on my machine resolved the issue..