After an update that I needed for another package, I can no longer use 'eeptools' to calculate the age. When I try, I always get the following error message:
Fehler: Laden von Paket oder Namensraum für ‘eeptools’ in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]): fehlgeschlagen
es gibt kein Paket namens ‘minqa’
I have already tried deleting the package from the location and reinstalling it. Loading the "Minqa" package also failed.
I am grateful for any tips!
Related
When I tried to run the library(semPlot) , always receive an error message:
library(semPlot)
Error: package or namespace load failed for ‘semPlot’:
objeto ‘readPNG’ não foi exportado por 'namespace:png'
Besides when I run the function sem Paths another error :
Error in semPaths(fit, title = FALSE, sizeMan = 4, sizeMan2 = 4, sizeLat = 4, :
could not find function "semPaths"
Could someone help me?
I resolved this problem as follows:
Install semPlot using install.packages("semPlot")
Wait for the dependencies to install
Restart R
Invoke the install command again using install.packages("semPlot")
I found that this installed two remaining libraries (XML and semPlot) and I was able to continue my analysis.
I want to create a file in the local folder, so I have written the following code:
IAsyncOperation<StorageFile^>^ fileTask = Windows::Storage::ApplicationData::Current->LocalFolder->CreateFileAsync("example.dat");
But how should I handle the fileTask?
I have tried to call the GetResults-method, but then I get following exception:
Ausnahme ausgelöst bei 0x00007FFD211C7788 (KernelBase.dll) in Test.exe: 0x40080201: WinRT originate error (Parameter: 0x000000008000000E, 0x0000000000000040, 0x000000C00EBFC470).
Ausnahme ausgelöst bei 0x00007FFD211C7788 in Test.exe: Microsoft C++-Ausnahme: Platform::COMException ^ bei Speicherort 0x000000C00EBFC730. HRESULT:0x8000000E Eine Methode wurde zu einem unerwarteten Zeitpunkt aufgerufen.
WinRT-Informationen: Eine Methode wurde zu einem unerwarteten Zeitpunkt aufgerufen.
Next I have tried to use create_task:
create_task(Windows::Storage::ApplicationData::Current->LocalFolder->CreateFileAsync("example.dat")).then([this](StorageFile^ file)
{
// irrelevant
});
Exception:
Ausnahme ausgelöst bei 0x00007FFD211C7788 (KernelBase.dll) in Test.exe: 0x40080201: WinRT originate error (Parameter: 0x00000000800700B7, 0x0000000000000048, 0x000000A936DFB230).
Ausnahme ausgelöst bei 0x00007FFD211C7788 (KernelBase.dll) in Test.exe: 0xE06D7363: Microsoft C++ Exception (Parameter: 0xCCCCCCCC19930520, 0x000000A936DFB830, 0x00007FFD01398AD0, 0x00007FFD012C0000).
Sorry for the language
How could I solve this Problem?
Next I have tried to use create_task...
You are in the correct direction. It is recommended to use task class for async operation.
But the file example.dat is probably already there when you call the GetResults. Thus you won't be able to use create_task(Windows::Storage::ApplicationData::Current->LocalFolder->CreateFileAsync("example.dat")).then([this](StorageFile^ file) to create the file again.
To fix the problem, just modify the codes like below:
#include <ppltasks.h>
create_task(Windows::Storage::ApplicationData::Current->LocalFolder->CreateFileAsync("example.dat", CreationCollisionOption::ReplaceExisting)).then([this](StorageFile^ file)
{
});
Added CreationCollisionOption::ReplaceExisting so that everytime the new file will replace the old file. And don't forget to include the ppltask.h.
I have registered global Exceptionhandlers in my Application (C#, WPF, .NET4) at the startup-routine on the following way:
AppDomain.CurrentDomain.UnhandledException += (sender, args) => HandleException(args.ExceptionObject as Exception);
Application.Current.DispatcherUnhandledException += (sender, args) => {
HandleException(args.Exception);
args.Handled = true;
};
Where HandleException() does logging the Exception and showing a MessageBox with some additional information.
Now, there are from time to time crashes of my application on some customer machines, where HandleException() is not called. Windows is showing the following message:
In the WindowsEventLog, I get the following entries:
Entry1:
Name der fehlerhaften Anwendung: proconact.exe, Version: 1.0.0.1365, Zeitstempel: 0x511531df
Name des fehlerhaften Moduls: PresentationFramework.ni.dll, Version: 4.0.30319.588, Zeitstempel: 0x504db27d
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x002ef05b
ID des fehlerhaften Prozesses: 0x1bec
Startzeit der fehlerhaften Anwendung: 0x01ce0b5dce4030a6
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\proconact_sck\proconact.exe
Pfad des fehlerhaften Moduls: C:\windows\assembly\NativeImages_v4.0.30319_32\PresentationFramewo#\c627e9b7f10b01db43645284e601f255\PresentationFramework.ni.dll
Berichtskennung: d8d69f94-777a-11e2-b4b0-b4b52f2aad4f
Entry2:
Fehlerbucket 3482664247, Typ 5
Ereignisname: CLR20r3
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Problemsignatur:
P1: proconact.exe
P2: 1.0.0.1365
P3: 511531df
P4: PresentationFramework
P5: 4.0.0.0
P6: 504db27d
P7: 329d
P8: 0
P9: System.StackOverflowException
P10:
Angefügte Dateien:
d:\Temp\WER6E9F.tmp.WERInternalMetadata.xml
Diese Dateien befinden sich möglicherweise hier:
C:\Users\roger\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_proconact.exe_b0fabce1f86d1f843de5b5b4692a3e8ecd928_2c77f03d
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: d8d69f94-777a-11e2-b4b0-b4b52f2aad4f
Berichtstatus: 0
What can I do that I can handle the Exception (for the meanreason to get the stacktrace for analysis where the exception occurs)?
Some exceptions cannot be caught, not even by AppDomain.UnhandledException. Because they are too nasty to permit managed code to keep running.
StackOverflowException is heart attack like that, infamous enough to give this web site its name. There is not enough stack space left to do common managed code execution duties, like running the jitter. ExecutionEngineException is another one, triggered by a destroyed garbage-collected heap and uncatchable in .NET 4.0 and up.
So no, the show is over and the WER dialog and the Windows event log entry is all that's left to look at. SO is always caused by a bug, you'll need to fix it.
I have developed one Installer Package using PackageMaker which installs different components in user machine. After signing the package its failing in another user machine with following error in logs. It works wihout any issue with un signed .pkg file
11/4/11 7:24:37 AM installd[718] PackageKit: Install Failed: (null)
Error Domain=PKInstallErrorDomain Code=102 UserInfo=0x1004261f0 "The package “_Installer” is untrusted." Underlying Error=(Error Domain=NSOSStatusErrorDomain Code=-2147409622 UserInfo=0x10043b2e0 "The operation couldn’t be completed. CSSMERR_TP_NOT_TRUSTED") {
NSLocalizedDescription = "The package \U201cInstaller\U201d is untrusted.";
NSURL = "#plugin.pkg -- file://localhost/Users/sandeepakhare/Documents/%20Apps/1025/Installer/Installer.pkg";
NSUnderlyingError = "Error Domain=NSOSStatusErrorDomain Code=-2147409622 UserInfo=0x10043b2e0 \"The operation couldn\U2019t be completed. CSSMERR_TP_NOT_TRUSTED\"";
I have used Verisigned Certificate to sign the .pkg .. Please advice
When i want to implement SQLite in a WPF-Application (.Net Framework 4), the programm failed (in the debugger-mode) with this message:
"Eine Ausnahme (erste Chance) des Typs "System.Windows.Markup.XamlParseException" ist in PresentationFramework.dll aufgetreten.
Zusätzliche Informationen: Zeilennummer "3" und Zeilenposition "9" von "Durch den Aufruf des Konstruktors für Typ "Kasse.MainWindow", der den angegebenen Bindungseinschränkungen entspricht, wurde eine Ausnahme ausgelöst.".
(this is german, here is the version, that is translated by Google-Translator):
An exception (first chance) of type System.Windows.Markup.XamlParseException 'occurred in PresentationFramework.dll.
Additional information: line number "3 " and line position "9 " "By calling the constructor for type Kasse.MainWindow" which matches the specified binding constraints, was an exception.
What should i do?
Greetings,
GreenPepper
This probably means that you are getting an exception in the constructor of the code-behind class of your window. Try setting a breakpoint and step through your constructor.