Unexpected error during Oracle Service Bus synchronization. Please see the logs for more information.
I have created a OSB cofiguration. I am trying to import OSB projects from the repository. When i drag and drop my osb project in my configuration. Its giving me this error.
I faced the same error, and I tried removing, reconfiguring OSB configuration files and OSB projects again and again but failed. At last I found out that if any of your WSDL is in invalid state it will show the above error because it is some conflict with metadata.
Just close the eclipse and go to this path /workspace/.metadata/.plugins/org.eclipse.wst.server.core/publish and delete publish0.dat file and other files also. Start the eclipse.
Its a Known ALSB bug in OSB (Eclipse) workspace. you should not drag-and-drop projects (or) artifcats between projects. Rather use cut-copy-paste for moving artifacts and import-export for creating and moving artifacts between workspaces.
Related
I am trying to serve 2 files needed by javascript for a web assembly package. The files example.wasm and example.data are in the public folder in the react js project file structure. When running with a development server using npm start, the files can be found by the project and can be read correctly. When building the project the files end up in the root directory of the project as expected. In spite of using the current PUBLIC_URL path for the files, the files can not be found, but the paths in the web console seem to be correct.
I am hosting the reactjs app from IIS 7.
Can you help me with the process to debug the problem described above?
Thank you in advance for your help.
After the help of #LexLi I have enabled the Failed Request Tracing Module in the IIS following this documentation:
[https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis][1]
Reading the log generated by the Failed Request Tracing Module I saw that when requesting the files example.wasm and example.data from the server the actual error was not 404 Not Found but:
SECURITY_DENIED_BY_MIMEMAP
After googling the error above I realized that the Default MIME Types configured in the IIS do not include files with extensions .data and .wasm. After adding those MIME Types to the IIS configuration using the MIME Type Module in the Web Server Level in IIS Management and restarting the server the problem was resolved.
After setting up the configuration for pipeline and clicking on debug in eclipse, I get this error.
Errors occurred during the build.
Errors running builder 'Digital Server Upload' on project 'DigitalServer'.
Tree element '/' not found.
If you don’t need to edit Pipelines, I recommend VS Code with the Prophet plugin. Check it out on the VS Code plugin marketplace.
https://marketplace.visualstudio.com/items?itemName=SqrTT.prophet
Check the project references (right click > Properties > Project References) of your connection to the instance. You likely have a closed or missing cartridge project referenced there. Once you remove this reference, the error will be gone.
I'm using the IBM Watson-Conversation example on how to connect to Facebook. But I can't get past copying the connector info to Github. I'm following the automated process but I keep getting the error below. Can't see any issues on Github, and the repository is empty. Any thoughts?
The integration could not be set up. Check the settings and try again.
Reason: An error occurred while cloning the git repository. Error details: Invalid repository URL. Unable to connect to: https://github.com/davidmackenziejtge/conversation-connector-1.git. Please go to GitHub to either delete or rename the empty repository before trying again.
Looks like you haven't given the automated process write access to your github repository. This would have been through a browser message asking for permission when you initiated the process.
I'm trying to debug a really bizarre issue. As part of the build process on a project I'm working on, a bower_components folder is created with all the packages listed in the bower.json file. This process seems to complete successfully. However, when I refresh the project and view it in the browser, there is a single missing package (in this specific case it is angular-ui-sortable). The package is present in bower_components directory on the server, but absent when viewing that same directory in Chrome devtools. The missing package is breaking the UI since Angular throws an "$injector error" because it is unable to find the missing package. The question I have is, how do i even begin to debug this issue. I've confirmed that I'm looking at the correct folder as well as checked the missing package's permissions. I've also confirmed that the package is correctly included in the project's index.html file.
Any advice is greatly appreciated.
Thank you.
I'm kicking the tires on the preview for the Visual Studio Team Services new Release Management system. My scenario is a classic website (ASP.NET 4.5) with a Git repo hosted in VSTS. The build definition is successful as seen here:
It is set up to publish as an artifact that can be picked up by Release Manager as shown here:
On the Release Manager side I have that artifact linked properly as shown here:
And here you can see my environments as well as the associated tasks (all 3 are clones)
When I run the release the build publishes fine, it connects to my subscription but when it attempts to find the package file it has the following error on line 101 of the output log:
"No files were found to deploy with the search pattern 'C:\a\4fe43dd1a***.zip'"
Here is the full output:
This is where I am stuck as I assumed my artifact link via VSTS should resolve this path for me. Obviously I am missing an important piece of the puzzle somewhere, but I've followed the available documentation as best as I can.
If anyone has a solution or can point me in the right direction it would be much appreciated!
--- EDIT ---
I used the file picker to select a web deploy package (see below). I tried using the root website as well as the bin folder. Both attempts results in an error stating: "No files were found to deploy with search pattern 'C:\a\4fe43dd1a\Classic Website Definition\drop\ClassicWebsite\bin'"
--- EDIT 2 ---
I added an MSBuild task to my BUILD process with the following MSBuildArguments
/p:OutDir=$(build.stagingDirectory) /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true
and in my Copy/Publish Artifacts task I limited my output to only copy .zip files. Now in my RELEASE process when I navigate to find a "Web Deploy Package" the "drop" folder is empty. Here is a screenshot:
I think I'm on the right path, I just need help figuring out to tune my BUILD tasks to generate the right artifacts for my RELEASE process to use. Any help would be appreciated.
The deploy package isn't copied to artifacts folder. That's why the release management cannot find the package. Setting "Copy and Publish Build Artifacts" to the following should fix your problem:
Change $(System.DefaultWorkingDirectory) to $(Agent.ReleaseDirectory). The artifacts will be put in that folder. I don't know exactly what $(System.DefaultWorkingDirectory) maps to, but my impression is that it's something outside of the folder used by the agent for your release.
Also make sure that the published artifacts contains the expected zip file -- if the deployment package isn't getting created, or if you're not publishing the output folder that contains the package, obviously you won't be able to release it later.
When you build your web application, make sure it's packaging for deployment by using MSBuild arguments that package it up. Something like this should work:
/p:OutDir=$(build.stagingDirectory) /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true