I Got this Error But i'm created all folders in Lightning Experience Reports & Dashboards Specialist Super Badge
Any on help ...
We can't find the correct access configuration for the SolarBot Support Reports folder
Related
I'm using two laptops and stored my C# code in OneDrive.
I am aware that sharing code via OneDrive is not be the best approach, but that's what I'm dealing with now.
I noticed that on laptop 1 I have to define the following path to the data file (mdf):
C:\Users\ Diet\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
On laptop 2, the path is different because the user I'm logged in with has a different name (or at least that's what I believe is the cause)
C:\Users\ Dieter\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
Updating this in the Web.config fixed the connection to the database, BUT building the solution still returns an error, also related to a cloud operation, hence why I think it is caused by the path in OneDrive...
The error message:
CSC : error CS0041: Unexpected error writing debug information -- 'The cloud operation was unsuccessful.
I welcome your insights. Thank you for helping me out.
I have my projects stored in OneDrive and had this same issue. The fix was to set the entire Project folder contents to "Always keep on this device".
Seems that building the solution in VS was attempting to write to files that were not cached locally from OneDrive. As soon as I changed the setting, the build worked!
I was also storing my project on OneDrive, got the same error after installing a new ssd.
Rebuilding the solution was enough for me.
I am getting component-preload.js not found error even tough it exists..
I'm using SAP WEBIDE personal edition full stack. so, neo-app.js and package.json are generated by defalut and by using the build option I generated component.-preload.js along with dist folder.As in my project I dont have direct connection to the SAP system,I need to use export(from webide) and import/download(using UI5/UI5/REPOSITORY_LOAD) into my front end server.Once I upload the project into the front end server component-preload.js is missing so am getting the same error "Component-preload.js missing" even though it exists.
could some one please let me know what could be the problem and how to resolve it.
Thanks in advance!
I hope someone can help, this is my first question ever because I've never been as stuck as this before!
I have an on premise QA server running Microsoft Dynamics 2015 CRM running on Windows Server 2012. It contains approx 30 customisation solutions from various previous sources unknown to me.
After installing ADX Studio Solutions, the system becomes modified and overwrites some/all of the previous customisations back to defaults. The symptom is that Entity names and fields etc. are reverted back.
So it is required to re-install a previous backup of the solution after installing the ADX parts. This solution is exported as a "Default Solution" prior to installing ADX Studio in a file called "Default_1_0.zip".
The problem is that the import fails when trying to import the backed up solution after having installed an ADX Studio solution.
The backup comes from the same server Dynamics instance, it's not being moved anywhere.
The process is:
Backup entire "Default Solution"
Install ADX Studio and and "Basic Portal" solution components
Import previous backed up "Default Solution" to re-apply the changes overwritten by ADX Studio.
This is a screenshot of the import screen showing the failure:
The log file xml has a "Solution" and a "Components" section. The Solution Section looks like this:
Solution
Name Default
Display Name Default Solution
Description Solution that contains all components in the system
Version 1.0
Package Type Unmanaged
Publisher
Name DefaultPublisherCLIENT
Display Name Default Publisher for CLIENT
Description Default publisher for this organization
Email
Website
City
Country/Region
Street 1
Street 2
ZIP/Postal Code
State/Province
Phone
Status Failure
Message An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.
Progress [%] 99.96
Duration [s] 730.9
As you can see, it gets to 99.96%.
The "Components" section contains one error on line 2781 that looks like this:
Root Components Insertion Failure 0x8004F018 This item is not a valid solution component. For more information about solution components, see the Microsoft Dynamics CRM SDK documentation.
Dependencies Calculation Unprocessed
All previous rows are logged as "Processed".
I am in no way a Dynamics or ADX Studio expert so I'm trying to find out if anybody has any answers which may be relevant.
Some more details:
Obviously I've tried searching for answers and also tried using the crmdiagtool2011 tool, which has not yet proved useful to me.
I've also tried implementing this solution: Microsoft Forums
But the error code and message is slightly different and this solution did not work for me.
I have managed to overcome a previous issue with importing the solution which was very similar to this one: Magnetism Solutions
Their "option 2" involved manually editing the solution.xml and customizations.xml files of the backup which I did and it seemed to overcome that particular problem. I didn't know how to achieve their "option 1" so that wasn't an option for me.
We use Coverity's free scanning service for free and open source projects. We have not been able to utilize the service for the last two months or so. Prior to the service failures, we had half-a-dozen or so good analysis.
Submitting a scan results in:
Last Build Status: Failed. Your build has failed due to the following reason. Please fix the error and upload the build again.
Error details: :Failed to retrieve tar file
Coverity is very good about providing copy/paste directions, and we have copied/pasted them religiously. We verified there are no build errors, and we verified the build ends with "131 C/C++ compilation units (100%) are ready for analysis" and "The cov-build utility completed successfully".
We've tried to resolve the issue by verifying things from this generic solution provided in a "failed email" response from the service. We verified or performed all of them except number four.
We did not perform number four because Coverity's documentation is horrible (its the exact opposite of their awesome scanning service). Because there's no instructions or RTFM to read, we have no idea which knobs should be turned for bin/cov-configure. We don't want to mess with it since it worked in the past.
We also tried the following:
using the web submission form and browser
using curl from the command line
packaging cov-int/ in a tarball
packaging cov-int/ in a zip file
using all lowercase for the project name
capitalizing the first letter of the project name
We always get the same message ("Failed to retrieve tar file"), even with a ZIP file. Recall that prior to about 6 weeks ago, everything was working fine.
What is the secret to uploading a file to the service? What has changed in the last six weeks or two months?
After contacting the coverity support we just received the following answer and we could successfully submit a build. Seems there was some hickup on the coverity side.
"This was due to some behind the
scenes issues on our end – nothing interesting,, but it is back up and
running now. Thanks for your patience".
iam creating setup file in ado.net but whenever i build my project it is give me 'oledb32.dll' should be excluded because its source file 'C:\Program Files\Common Files\System\Ole DB\oledb32.dll' is under Windows System File Protection error so that's why i download in net and try to import that dll in my project but this file cannot import detected dependencies folder ..oledb32.dll file is important for show patient details in excel format so can you all expert give me any suggestion or advice
I ran into this issue as well and couldn't find a concrete answer until now.
I'm using a development box, checking in code via SVN, and running CruiseControl.NET to execute devenv.exe to automatically build the project (I don't use MSBuild because Microsoft hasn't implemented a solution for building Setup projects yet, and I assume this is what you are also using). The setup project would build fine on the dev box but on the build server it kept coming up with that same error.
The MSDN explanation can be found here, it's not very descriptive, but that's basically what needs to be done. The more concrete answer can be found here. Basically you have to open up VS on your build server and go in and exclude oledb32.dll (and any other problem files) and voila it finally builds and creates the MSI file! Hope this was helpful for you.