Re: N1MM fails to start. No message on screen.
I could check NTFS perms, but it’s a moot point because It’s working. However, it seems odd that I renamed it to .old to make it “not found”, yet N1MM+ it realized the name was changed and tried anyway. I did look at NTFS perms for both the .old version and the newly installed version. At first glance they look the same. To be sure, I’d have to create a document as Windows does not give me a way to create a list of perms for both old and new install. There are tens, if not hundreds of setting to remember. If I had such a list I could compare in detail. I don’t want to build that list as its now working.
I believe the root cause is moving my docs from \\FS1 to \\FS2, yet something insisted on going to \\FS1 and that server is “gone”. It probably retried X number of times, and eventually just gave up and exited the program. I need to remember to not do that.
I probably could have just done the uninstall / reinstall on my own without posting to list, yes I know the uninstall is not needed. Sorry to bother you.
Anyway, its working, thanks for the help.
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of John Bednar
Sent: Sunday, May 13, 2018 8:07 PM
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.
The cause of the error is that access to C:\Program Files (x86)\N1MM Logger+.old\LogError.txt is denied.
This is not a N1MM Logger+ issue.
I renamed. It went further with “A runtime error occurred during error processing” . That message is below, but I think may get stripped out.
Running the Full Installer, boot, Run Updater worked on 2nd try. First time it hung trying to go to a non-existent file server (that was my clue). I told it c:\N1MM Logger+ instead. It created it, but it’s still empty. It did find my old databases in the Docs folder. While running installer it was trying to go to a non-existent file server which I rebuilt under a new name months ago. \\FS2\Docs versus \\FS1\Docs. Windows document folder is redirected there. Changing File Server name probably was the root cause. Rather than go to the docs folder, it insisted to going to the location of the old docs folder. Had it simply looked at whatever Docs was pointing at it would have worked. Not sure if that is a Windows issue or N1MM, but it’s a minor issue now that I know about it.
Thanks for your help.
I’ll try that. I have no data to save. I exported and imported into my general logger at end of last contest.
I would rename the user N1MM Logger+ directory and start the program. The default location of the directory is MyDocuments. If the program starts your database file(s) are corrupt.
If it doesn’t start, the installation is damaged, likely from a computer scan or hardware issue. Rerun the Full Installer. There is no need to un-install. If the installer tells you to reboot, then restart the computer. Install the latest update before starting the program for the first time.
Make sure the database directory is located on the computer physical disk drive (not on a network share, cloud, USB disk, etc).
Some computer virus/security programs are known to damage the installation.
Never allow shadow backup of the database directory files when the program is running.
No. It was first installed 2-3 years ago. Windows 10 has been upgraded several times via the forced updates. It is now at 1709, Build 16299.431 .
Is this a new install?
I’m getting ready for June VHF. N1MM fails to start. No error message on screen. I extracted this from Windows Application log. I was thinking about uninstall / reinstall but perhaps there is a better way?
7 3 Bob
App log follows---------------------------------------
Log Name: Application
Source: Windows Error Reporting
Date: 5/12/2018 3:08:07 PM
Event ID: 1001
Task Category: None
Fault bucket 1662346856206063835, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 57f12cba-5edf-4956-b876-3182caa9ea08
Report Status: 268435456
Hashed bucket: fbcaf3ef94aeb5d9a711d7a881a658db
<Provider Name="Windows Error Reporting" />
<TimeCreated SystemTime="2018-05-12T19:08:07.138031200Z" />