We have a Cloud Service that we have been deploying/updating without issue. In the past two weeks every time we try to deploy the package we are getting the error "Deployment could not be created - There was an error processing your request. Try again in a few moments".
I am at a loss as to how to even debug the issue to get more detail. if anybody has any advice on how to get a better error description would be appreciated.
The only changes in this deployment are some changes to the static files in the package so it is unclear what is causing the issue. The process we use is (1) build the package, (2) upload the package, (3) deploy in the staging environment. The package gets uploaded but fails to deploy (step 3).
Any help as to what the issue is or how to get better diagnostic information woudl be great.
Related
When uploading the wasm binary, as a compiled smart contract on the 'ink-workshop' - the canvas-ui that I am running just errors.
Canvas-ui error:
Uncaught error. Something went wrong with the query and rendering of this component.
Cannot read properties of undefined (reading 'args')
Step: 'Drag the flipper.contract file that contains the bundled wasm blob....'
The Github issues section associated is read-only, hence why I am posting here. Anyone know what might be the problem here?
Incase others are wondering what to do in this instance. I was able to deploy using the official polkadot web interface.
Connect your local running node via settings and there you can deploy your flipper contract.
This is a good article on the astar network docs on how to do it, using the basic flipper contract example.
There is a maintenance problem and they wanna fix it.
https://github.com/paritytech/canvas-ui/issues/119#issuecomment-1020114242
When I try to deploy a SSAS Tabular project from my local machine to the integration server I get an error in the metadata. It's a many to many error that I had previously solved, and I know I solved it because the Tabular project can be processed locally. That is the crux of the issue, when I process the project, it is using the correct data source, but when I try to deploy the project it uses a previous data source that is no longer valid.
Steps I've taken:
I Went into the model, selected existing connections, and modified them to connect to the correct environment (they were previously pointed at the invalid environment) this allowed me to process the data, but I still can not deploy correctly.
I created a new configuration in the configuration manager, to no avail.
I looked for other areas where the source DB is listed, I haven't found any, which is frustrating because I know it's somewhere.
Is there a cache I'm missing or a setting I didn't check, any help would be appreciated, thank you.
I had upload jar to server, but I got below error. I had tried so many times.
And then I log into https://oss.sonatype.org/#stagingRepositories, I can see the list of Staging Repositories, but I cannot drop or release the repository. It said 403.
Could any one help me ? Thanks a lot.
Your account doesn't have permissions to perform these actions.
This isn't the right place to ask for help with this, file an issue at https://issues.sonatype.org in the "Community Support - Open Source Project Repository Hosting (OSSRH)" project.
I am currenlty using Web Deploy 3 with Automatic Backup. Yesterday, backup failed with error message 'ERROR_PACKAGE_TOO_LARGE'.
as per MSDN
Resolution - Use the archiveDir provider when creating a package instead. Currently there is no solution for this limit with respect to automatic backups.
Now archiveDir works fine on command line
msdeploy -verb:sync -source:apphostconfig="Site" -dest:archivedir=c:\archive
I am pretty new to Web Deploy, can someone please help me to automate this with Web Deploy using VS2013? I don't want to login to server to manually back up my site and then come back to VS to publish. Is there any setting in .pubxml(Publish Profile) to achieve it?
Thanks
I'm trying to deploy an existing build with the "LabDefaultTemplate.11.xaml".
My problem is, that the build times out, as soon as I use an existing build. Here are the last steps including details and the timeout exception:
See http://i.stack.imgur.com/po1i6.png
I have two different servers. The first has TFS 2013 with Build Service, Controller and Agent installed on it. The second is thought to be used for Testing and has a Test-Controller and Agent on it (configured as a Standard-Environment in MS Test-Manager).
Build Service Account is a Domain-Admin
Build Connection to TFS goes with a TFS-Admin
Test Controller Service Login Account is a Local-Admin (mirrored on the Build-Server) and earlier tried with the Domain-Admin
Test Controller TFS-Connection also with a TFS-Admin
Test Controller Lab Service Account is not used, earlier also tried with the Domain-Admin
When I set the build to use the latest TFS-Build it runs into the timeout.
And when i set the path to use a Build from a specific location to the Build Directory on the Build-Server it all just works fine.
The difference between a working build and the timeout described above can be seen in this picture: http://i.stack.imgur.com/gPM07.png
Has anyone an idea where I'm struggling?
The problem was, that my previous builds only "partially succeeded" because they had some failing unit tests. The setting to use the only uses fully successful builds. So the latest build which was used had no drop folder configured.
I received no info about that, until I saw it in the logs. My fault was to never check, which build really is used as the latest.