I have a flow running within a project named 'dm' that was created by someone else.
This flow works well.
I Right click and hit "Copy", and then I hit "Paste", and chose the project name 'dm_1'. All looks well
So I try to run the new project, I right click on the flow and hit "Run As - Mule Application"
Immediately I get the following error:
Launching dm_1 has encountered a problem.
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft or post a message in the MuleSoft Community Forums (http:/forum.mulesoft.org) with a detailed description of how you encountered the problem
DETAILS:
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft Support or post a message on the MuleSoft community forums (http://forum.mulesoft.org) with a detailed description of how you encountered the problem.
Project referenced by launch does not exist.
So how do I fix this problem.
I do not see anything within the xml that would suggest there is a project name that needs to be changed as well, with the possible exception of the following line:
<mulexml:schema-validation-filter schemaLocations="C:\Users\xxx\AnypointStudio\workspace\dm\src\main\resources\p.xsd" returnResult="false" doc:name="Schema Validation"/>
Where do I look to change the project name
try adding a new flow to the same project. Then right click on the new flow and run it. This will cause the entire project to run.
Related
I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.
I have a label in my project
When I queue a build, and put the label in the "Source Version" field, prefixed with a L, it always comes up the following error:
500: TF14064: Could not find label mylabel#$/.
Anyone been able to get this functionality to work?
Most likely the problem is that your label is not collection-scoped and therefore you need to provide a scope with your label. If you created your label in Visual Studio, the scope is probably project-scoped. So for example if your label is 'mylabel' and your project name is 'myproject' then in the Source Version field you should enter this:
Lmylabel#$/myproject
Here are a couple links that help explain labels and scopes if you are interested.
https://msdn.microsoft.com/en-us/library/9ew32kd1(v=vs.100).aspx
http://teamfoundation.blogspot.com/2008/03/label-scope-revealed.html
I'll update the Microsoft Connect Page with this information too.
I can reproduce this issue and have help you submit a feedback on Microsoft Connect Page, you can track the status here: https://connect.microsoft.com/VisualStudio/feedback/details/2345698/500-tf14064-could-not-find-label-error-occurs-when-queue-a-build-with-specified-label
I was facing the same issue for TFS build and the error says like: “Cannot find the current label tfs build”.
How to resolve the issue:
Go to Configuration of your TFS build
Make the Label sources as true
Build the solution now and it's building fine.
Please reach out if any issues.
I'm following the tutorial at https://cloud.google.com/nodejs/getting-started/using-cloud-sql and hit an issue with the section "Configure the new Cloud SQL instance".
Basically, I can't click "Save" successfully when entering the "0.0.0.0/0" network configuration. Chrome's Javascript Console shows an error "Custom HTML/JavaScript blocked. See go/13687728."
What's going on?
I tried continuing with the tutorial but hit an issue at the "npm run-script init-cloudsql" step.
Thanks for the help / fix!
I found a work around that might get you moving:
Click Add Item, Enter details, then click Save. Do not add another until the done message appears.
I am using "parse.com" in my application. I just bought a new system and i want to shift my project in new mac but in new mac my project makes issue of "Parse Issue" and error "Expected a type". While on my old system it is working really fine.
These errors are coming in my frame work "Parse.framework" and file "PFFacebookUtils.h".
I clean my project and build I quit my xcode then build but in vain. Kindly help me to run it on new system. Pic is attached also and if someone wants me to upload code then kindly tell me
In your projects build phases make sure that your framework is listed under link binaries
I got fixed my problem. It was really weird problem for as it is a generic error. It was not showing any clue. My problem is fixed when i just added the latest version of facebookSDK in my documents folder.
I have this Metro App project that I just tried building for the Windows Store.
After completing the buildprocess (with no errors) I can't open the appxmanifest xml file in visual studio anymore. If I select "STORE" > "Edit App Manifest" I get the following error message: "Value does not fall within the expected range."
I can't open any manifest file in any project now.
Does anybody know whats happening, do I need to reinstall Visual Studio or whats going on?
I'm pretty desperate, so any suggestions are welcome.
Found the answer here http://forums.asp.net/t/1836720.aspx/ - so i tried deleting the .suo files from the project, and now it seems to work. I have no clue why that would affect newly created/other/checked out projects, weird behavior indeed?
(Since I am both new to SO and to Visual Studio, I don't know if answering my own question is considered bad practice, if it is, please let me know what I should do instead)
It's an XML file, so you could try to open it with a text editor to figure out if there's an invalid value set somewhere. You could always compare to a default Package.appxmanifest from a new project.
Can your fellow coworker open the manifesting file you're having trouble with?
The first thing to check is to make sure you are running Visual Studio as an admin. (Right click, run as administrator)
Try creating a completely new project. Save it without modifications. Build it. See if you can open the manifesting file in that project. If you can't, try a XAML/C# project instead of JS just to see if something is wrong with the specific project type.
And before you try completely reinstalling, you might try resetting your Visual Studio settings. Make sure to take a backup just in case you need to get your environment back to where it was once you find the issue.
http://msdn.microsoft.com/en-us/library/ms247075.aspx