Announcement

Collapse
No announcement yet.

Snapshot produces fatal error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Snapshot produces fatal error

    I'm currently developing three shopping carts for various customers. On two of the carts I can export snapshots without a problem. But on the third installation it produces a fatal error and crashes.

    How can I resolve this with re-installation and the loss of a weeks work?

    #2
    Whats the error you are getting as a reason for the Fatal Error
    Owner of a broken heart

    Comment


      #3
      Just to reassure you, you can always back up your site directory manually (e.g. 'Sites\Site1') in order to protect your work, even if you aren't able to take a snapshot.

      It would be good to see the error message you received.

      Comment


        #4
        The error message is as follows:

        http://www.siteeng.co.uk/actinicerror.gif

        or

        http://www.siteeng.co.uk/snapshoterror.txt

        Comment


          #5
          i had the same problem

          so i assumed it was something to do with the updating of the database and tried the compact (catalog) command

          this takes you out of actinic

          and when you come in again and do a snapshot | export, it works

          (the same effect occurs if you exit actinic, go into ms access and compact the site1/.mdb file)

          ...seems that there's a little glitch in actinic update mechanism of the database... which could give a heart attack to some when they see the word 'fatal' and think that the last few hours' work has been wasted...

          Comment


            #6
            Thanks for the tip - I tried the Compact Database command as you suggested, but it doesn't cure the snapshot error for me.



            Originally posted by harry
            i had the same problem

            so i assumed it was something to do with the updating of the database and tried the compact (catalog) command

            this takes you out of actinic

            and when you come in again and do a snapshot | export, it works

            (the same effect occurs if you exit actinic, go into ms access and compact the site1/.mdb file)

            ...seems that there's a little glitch in actinic update mechanism of the database... which could give a heart attack to some when they see the word 'fatal' and think that the last few hours' work has been wasted...

            Comment


              #7
              All I can think of doing is uninstalling and re-installing Actinic.

              There are some tips for doing this in this thread - although you will have to back up all three of your site folders, and record all three sets of security data, and then refresh all three sites.

              The alternative is if you have a spare PC there, install Developer on that PC and copy across the site directory and security settings from the faulty site into the new installation and see if you can take a snapshot.

              If you can then maybe you can delete the faulty site from your original installation, then re-add the site, then import the snapshot taken from the new installation.

              Comment


                #8
                Hi there

                Someone else has had a similar crash on snapshot and managed to fix it by opening the ActinicCatalog.mdb database in Access and selecting 'Tools | Database Utilities | Compact and Repair Database...'

                Something to try if you haven't done the other suggestions...

                Comment


                  #9
                  This didn't work either.

                  I thought I'd export the catalog using the csv method and rework my changes after deleting site one and start again.

                  Another Bug: The fragments I created didn't import as they are over 255 Characters long [according to the error report - see below]

                  Field data too long. The field Fragment text expected a string with less than 255 characters


                  Originally posted by cdicken
                  Hi there

                  Someone else has had a similar crash on snapshot and managed to fix it by opening the ActinicCatalog.mdb database in Access and selecting 'Tools | Database Utilities | Compact and Repair Database...'

                  Something to try if you haven't done the other suggestions...

                  Comment


                    #10
                    Interesting

                    I deleted all the fragments created in the original site [all well over 255 Characters long, more like 8-900 characters] now I can export the snapshot without it crashing but get the following error message:

                    Errors
                    (File ExportFiles.cpp, Line 563) - The file C:\Program Files\Actinic v7\Sites\Site1\navbg1.gif was not found System error 2 - The system cannot find the file specified.
                    ..
                    (File ExportFiles.cpp, Line 563) - The file C:\Program Files\Actinic v7\Sites\Site1\hdrftr.gif was not found System error 2 - The system cannot find the file specified.
                    ..
                    (File ExportFiles.cpp, Line 563) - The file C:\Program Files\Actinic v7\Sites\Site1\navbg2.gif was not found System error 2 - The system cannot find the file specified.
                    ..
                    (File ExportFiles.cpp, Line 563) - The file C:\Program Files\Actinic v7\Sites\Site1\catalog1.gif was not found System error 2 - The system cannot find the file specified.


                    So after C&P these files from other themes and have replaced all the fragments with non-selling products - I can now export a snapshot successfully.

                    A bug to be fixed perhaps?

                    Comment


                      #11
                      I have had fatal error on snapshot. I cured it by stopping all other programs and any network intensive applications running and then snapshot worked . . .

                      We do now have errors in every snapshot for files not found . . . which are exactly where they are supposed to be and Actinic thinks they are not!

                      Could this be somehow connected to the 'memory leakage' problem that was suggested before in http://community.actinic.com/showthr...ghlight=memory
                      Tony

                      Mandrake Press Ltd.
                      Actinic user since 1998

                      Comment


                        #12
                        I don't think the missing files will be to do with the memory leak - although it is possible that your difficulty actually taking the snapshot (having to shut down applications) is due to the v7 snapshot being more memory-intense than the v6 one.

                        Some people have fixed this by doing 'Tools | Database Utilities | Compact and Repair Databases...' in MS Access on the 'ActinicCatalog.mdb' database. Have you tried this.

                        With regards to the missing files, there is an old bug in v6 where if you switch sites and do a snapshot, Actinic looks for files from the site you were on previously - but this is fixed in v7. Do you have more than one site? ANd are you absolutely certain the files mentioned are present within your new v7 installation?

                        Comment


                          #13
                          Hi Chris

                          We have our active site at www..mandrake-press.com but we have been testing a duplicate site with All Affiliate Pro at www.mandrakepress.com.

                          We have two network setting files and import the appropriate one to access the relevant site.

                          We are about to go-live on the test and close down the old one.

                          As to missing files -- yes, I read the error message and made doubly sure they are where they are supposed to be. I just ran snapshot and one of the file messages is
                          (File ExportFiles.cpp, Line 563) - The file D:\Catalogue Files\TAROT CAT\tarotcat.pdf was not found System error 3 - The system cannot find the path specified.

                          . . . that file is exactly where it is supposed to be. Looking more carefully I see Dazzer and I have different error messages his relates to 'file' mine to 'path'.

                          Regarding using ms-access the problem has not re-occurred since we followed the procedure regarding other programs and network activity . . .


                          I also experienced upload problems where 'Business' would fail at the file merge stage. I rang in (cover customer) and said what was happening, that my site was down etc., and was promised revised scripts that day but never heard another thing . . . I persevered with upload attempts and the problem seemed to clear itself the next day. I did not follow up on my call to Actinic . . .
                          Tony

                          Mandrake Press Ltd.
                          Actinic user since 1998

                          Comment


                            #14
                            snapshot causes Actinic 7 Developer to crash

                            I am trying to deploy a site and all I get is a crash and 'Memory cannot be read errors' no other applications open.. 1.5 Gig of RAM....

                            The only way to deploy the site is to copy the whole lot onto the clients machine!

                            Desperate on launch day

                            Jason
                            http://www.healingbreeze.net

                            Comment


                              #15
                              Just copying the 'Site1' folder is the way to do it if snapshot is giving you all those errors. Remember to make a note of the details in 'Housekeeping | Security' as these are not carried in the database.

                              You can also try doing a 'Tools | Database Utilities | Compact and Repair' in Microsoft Access 2000 as this sometimes hits the spots which Actinic can't reach.

                              Comment

                              Working...
                              X