Chris - The output of the Debug routine is a text (.txt) file that is placed in your user home directory...just attach it to an e-mail addressed to support.

This message usually means that Omniscope was shut down somehow too abruptly on last use, or a severe crash which would normally mean an alpha or development build?

Without the debug file it is difficult to know what happened, but removing all Omniscope installations and re-installing to your account only can be the fastest way to get running again.

Hi Chris,

Can you also describe the issue in more details:
1) Which version/build you are using, operating system (Windows xp, Windows 7, etc).
2) Could you try to install another build (no uninstall needed).
3) Can you try to choose different options during the installation - "for current user"/"for this PC".

running Win7
Omniscope 2.8 build 641

Have uninstalled and rebooted PV then downloaded and intstalled latest build of 2.8 and still cannot start and get same error message

will send debug file as attachment in email to support@visokio.com

Chris - Can you follow the steps on this link under Troubleshooting in the KnowledgeBase:

http://www.visokio.com/kb/java-memory-fragmentation

Yes this has solved the problem on our first affected PC, we will try it in the others and we note that we need to upgrade to 64bit Windows....