1. Forum
  2. fsxNet
  3. FSX MYS

  • Mystic Error Log

    From Rick Smith@21:1/190 to All on Tue Mar 17 10:51:14 2020
    2020.22.02 09:03:26 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.22.02 13:43:01 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.22.02 18:04:57 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.23.02 09:08:20 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.26.02 08:40:59 MYSTIC 002 Theme does not exist: default
    2020.26.02 08:41:00 MYSTIC 002 Theme does not exist: default
    2020.26.02 15:14:44 MYSTIC 003 ERROR: Can't find xfer.log, error 2
    2020.26.02 15:53:37 MYSTIC 002 Irregular shutdown event
    2020.07.03 08:50:27 MYSTIC 001 Unable to access users file (5)
    2020.07.03 08:50:33 MYSTIC 001 Unable to access users file (5)
    2020.07.03 22:39:52 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.08.03 13:38:28 MYSTIC 001 Cannot write to c:\mystic\data\chat1.dat. Code=2 2020.08.03 14:20:22 MYSTIC 001 Unable to access users file (5)
    2020.08.03 14:20:23 MYSTIC 001 Unable to access users file (5)
    2020.08.03 14:20:23 MYSTIC 001 Unable to access users file (5)
    2020.13.03 00:27:00 MYSTIC 003 Cannot write to c:\mystic\data\chat3.dat. Code=2 2020.13.03 17:45:00 MYSTIC 003 Irregular shutdown event
    2020.15.03 04:00:08 MYSTIC 002 Unable to access users file (5)
    2020.15.03 04:00:12 MYSTIC 002 Unable to access users file (5)
    2020.16.03 04:00:13 MYSTIC 001 Unable to access users file (5)
    2020.16.03 04:00:17 MYSTIC 001 Unable to access users file (5)
    2020.16.03 04:00:17 MYSTIC 001 Unable to access users file (5)
    2020.16.03 21:51:00 MYSTIC 004 Theme does not exist: default

    Can anyone help me sort these errors or are they not important?

    Regards,

    Rick

    5

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
    * Origin: Abacus BBS (21:1/190)
  • From ryan@21:1/168 to Rick Smith on Wed Mar 18 18:41:56 2020
    Can anyone help me sort these errors or are they not important?

    These look probably important.

    When did you start seeing these? What was the specific action you took right before this started happening?

    If I had to venture a guess, I'd say it looks like probably a botched upgrade...if that's the case, let me know the version you were on previously and the version you upgraded to and the specific steps you took.

    --- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Nitro@21:1/190 to ryan on Thu Mar 19 10:20:22 2020
    When did you start seeing these? What was the specific action you took

    I dont believe I did anything but I am not sure I noticed anything besides happening on to the logs.


    If I had to venture a guess, I'd say it looks like probably a botched upgrade...if that's the case, let me know the version you were on previously and the version you upgraded to and the specific steps you

    Since setting up I did upgrade to .a45, I did try to upgrade to .a46 however MIS would not start in my setup, it started where I installed the .a46 fresh install. So I reverted back to backup. Today I have a new machine arriving that is capable of running 32 bit windows so my plan is to install the bbs on there, is there a way of doing fresh install and just copying over the data?

    All help appreciated and as always thankyou in advance.
    Regards,

    Nitro

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
    * Origin: Abacus BBS (21:1/190)
  • From ryan@21:1/168 to Nitro on Fri Mar 20 00:09:52 2020
    Since setting up I did upgrade to .a45, I did try to upgrade to .a46 however MIS would not start in my setup, it started where I installed
    the .a46 fresh install. So I reverted back to backup. Today I have a
    new machine arriving that is capable of running 32 bit windows so my
    plan is to install the bbs on there, is there a way of doing fresh
    install and just copying over the data?

    It sounds like something got botched in the upgrade. :/

    Also, when you do the upgrade, mis is not running at the time, right? And you run the 'upgrade' binary as well?

    I'm not sure about the data files, that's a great question for g00r00 :) Good luck!

    --- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Crew@21:1/103 to Nitro on Fri Mar 20 20:05:42 2020
    Hi,
    Since setting up I did upgrade to .a45, I did try to upgrade to .a46 however MIS would not start in my setup, it started where I installed
    the .a46 fresh install. So I reverted back to backup. Today I have a
    new machine arriving that is capable of running 32 bit windows so my
    plan is to install the bbs on there, is there a way of doing fresh
    install and just copying over the data?

    I had something similar, Mis won't start if some of the data files are from
    an old version I think. I ran the upgrade.exe file again then it started straight up.

    I had another little weird moment in that mis would not display messages at
    all but after closing the program next time around all was good.

    Hope this helps, Other people might have better help.

    Cheers
    Lloyd

    --- Mystic BBS v1.12 A46 2020/03/18 (Windows/32)
    * Origin: - Micro Link BBS - QLD, OZ (21:1/103)