Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
Tony,
Thanks for the reply; that link, however, appears to be a dead end. Please requote the intended link.
Thanks again,
Bill Zigrang
Sorry Bill, there was a space at the end of the link. I have updated it to the correct one. I apologize for the inconvenience.
“Unable to start the Integrator.Please reboot and try again(1007,157)”-- NSR V.2 (NSW 2008 Premier)
I am trying to back my computer up with Norton Save and Restore V.2 from Norton SystemWorks 2008 Premier; I want to run my backups with the computer in standby (sleep) mode. Thus, I have added a scheduled start to Norton Save and Restore under Windows Scheduler at the appropriate times. Although my backups appear to be performed correctly, when I “wake up” the computer the next morning I see the above error message repeated for each of the scheduled startup occurrences. ? Is it necessary to use Windows Scheduler (in addition to scheduling NSR backup) to perform a scheduled backup in sleep mode?? If so,what can I do to prevent the above occurrence?
Thanks in advance for your help,
Bill Zigrang
Hi Bill,
Please see the following document in the Symantec Knowledge Base for information on this error:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/0/f02350734698031488256d7f007681f5