I installed the NuGet package 'EmbeddedSTS' to test a proof of concept. It worked well and I was happy with the package.
I decided to remove the package. However, when I removed the EmbeddedSTS package and built my solution, I got the following error:
The pre-application start initialization method Start on type
Thinktecture.IdentityModel.EmbeddedSts.EmbeddedStstConfiguration threw
and exception with the following error message: ID7027 Could not
load the identity configuration because no
configuration section was found.
Am I missing a step to completely remove the EmbeddedSTS package?
When I check the installed packages on the solution, EmbeddedSTS is not there.
My question is NOT how to fix the error message; its how to remove the EmbededSTS from Visual Solution/ Solution
Many Thanks!
The answer was simple. There is a EmbeddedSTS DLL in the bin which is fired up each time you start debugging. By removing this DLL I was able to get my solution to build again.
Related
When I load the vega-lite data sets using
(vega:load-vega-examples)
I get the following error:
Could not REQUIRE CL-DATE-TIME-PARSER: circularity detected. Please check your configuration
However, the examples appear to have loaded.
Also, before I installed cl-date-time-parser in quicklisp, I was getting an error message similar to:
Do not know how to REQUIRE CL-DATE-TIME-PARSER
Does anyone know how to get rid of these errors?
Many thanks!
The IMDB example requires cl-date-time-parser. I suspect that problem is that (require ...) only works when the library is in a location known to ASDF. In a new installation, this may not be the case. Now reported as issue #19.
Try loading the library with quicklisp and then rerunning load-vega-examples.
I was trying to install the dplyr package on to my system but I am encountering the problem mentioned below:
install.packages("dplyr")
I got the error message
Error: Failed to lock directory "P:\Documents\R\win-library\3.6" for modifying try removing 'P:\Documents\R\win-library\3.6/00LOCK
I tried to follow the instruction by removing the 00LOCK file that was automatically created but that doesnt help as even after retrying to install the package after deleting the file I faced the same problem wherein the 00LOCK folder got automatically generated. Can some one please help me out in understanding why am I facing this issue and how to correct this error and download the packages.
I solved it with this pacman function that attempts to delete a 00LOCK(s) if it exists:
install.packages('pacman')
pacman::p_unlock()
It worked for me! Hope it works for you :)
I tried view(installed.packages()) to see where the packages are stored, post that I specified the path .libPath("path I saw in the installed.packages()") and then tried to rerun the installation and it worked.
I have been using roxygen2::roxygenise quite successfully with my package to build exported and imported functions. However, I recently ran into this error which I am unable to resolve:
> roxygen2::roxygenise()
First time using roxygen2. Upgrading automatically...
Error: File file does not exist
This is not the first time I have used roxygen2 with this package. In addition, I am not quite sure what "File file does not exist" means. Has anyone else seen this and been able to resolve it?
I think you have to set the working directory of R to be the package folder
I got the same error when using:
roxygen2::roxygenise("mypackage")
But, I didn't get the error when I instead used:
library(roxygen2)
roxygenise()
I know this is no explanation and I can't comment upon whether this works beyond my case.
i keep hitting this error today and I already download the plyr from github but it still doesn't work. I restarted R-studio even my PC after installing plyr..
It appears the problem may be due to a change made to the way R resolves references to external DLLs, as mentioned halfway through the thread here.
Adding the parameter PACKAGE="plyr" to the .Call function call on line 12 of R/loop_apply.R in the source (clone from github), and then installing the package from that source (install.packages("<path to plyr source>", type="source", repos=NULL)) seems to fix it.
I don't know what is going on, everything was working great but suddenly I started to have this error message on the documentation:
Error in fetch(key) : lazy-load database '......descopl.rdb' is
corrupt
I removed almost all my code and build again then publish to Github, but when I use the other laptop to download the package, the package is being downloaded and loaded but I can't call any of the functions, and the documentation states that error.
I don't know what caused the problem, I am using roxygen to generate the documentation.
https://github.com/WilliamKinaan/descopl
It seems that the error arises when the package cannot be decompressed by R (as #rawr established, it is corrupt). This solutions have worked for me:
1) Check for possible errors in the creation of the .Rdb files
2) Try restarting your R session (e.g. .rs.restartR() if in RStudio)
3) The package might have been installed in your computer (even though it does not work). Remove it using ?remove.packages()
I have had this problem with roxygen2 as well. Couldn't see any problem with any of my functions. In the end deleting the .rdb file and then getting roxygen2 to rebuild it seemed to solve the problem.
I think the explanation for what is causing this is here.
It's related to devtools.
Per #Zfunk
cd ~/Rlibs/descopl/help
rm *.rdb
Restart R. Look at the help for the package again. Fixed!
I received this error after re-installing a library whilst another R session was running.
Simply restarting the existing R session(s) solved for me (i.e. running .rs.restartR() to restart the sessions)
If you are using R-studio:
1) ctrl+shift+f10 to restart r session
2) tools -> Check for package updates -> update all packages
3) library(ggmap)
Problem is solved.
Basically all answers require restarting R to resolve the issue, but I found myself in an environment where I really didn't want to restart R.
I am posting here a somewhat hack-ish solution suggested by Jim Hester in a bug report about the lazy-load corruption issue.
The gist of it is that the package may have some vestigial S3 methods listed in session's .__S3MethodsTable__. environment. I don't have a very systematic way of identifying which S3 methods in that environment come from where, but I think a good place to start is the print methods, and looking for S3method registrations in the package's NAMESPACE.
You can then remove those S3 methods from the .__S3MethodsTable__. environment and try again, e.g.
rm(list="print.object", envir = get(".__S3MethodsTable__.", envir = baseenv()))
You may also need to unload some DLLs if some new messages come up like
no such symbol glue_ in package /usr/local/lib/R/site-library/glue/libs/glue.so
You can check getLoadedDLLs() to see which such files are loaded in your session. In the case of glue here, the following resolved the issue:
library.dynam.unload('glue', '/usr/local/lib/R/site-library/glue')
I got this error on RStudio on mac OS - updating all the packages and restarting r session did the trick.