7.2.7  
Download Now
 
 

Sawmill Discussion Forum

Subject: "sawmill6cl.exe going 100% even when I kill it" Archived thread - Read only
 
  Previous Topic | Next Topic
Printer-friendly copy     Email this topic to a friend    
Conferences Support Topic #1207
Reading Topic #1207
David Ryan
unregistered user
Oct-22-03, 02:57 AM (PDT)
 
"sawmill6cl.exe going 100% even when I kill it"
 
   Hi there.

6.5.0 was going reasonably well and then I upgraded to 6.5.3 by copying sa*.* from the \sawmill directory of a new install - this is the correct way, isn't it ?

Now when I go to update the database (or build it from scratch in fact) sawmill6cl.exe goes to 100% processor and doesn't stop. I managed to get into the admin menu and see that the only reported process is the server. When I kill the server I still have sawmill6cl.exe running away. If I go into task manager and kill the process all is well (except I don't have any data added to my database).

Any suggestions ?

Unfortunately I don't think I kept the old sa*.* files from the 6.5.0, so I'm not sure where to go from here. I could rebuild the whole configuration, but to be honest it took quite a while to build and I'm not entirely sure I could rebuild it quite the same way.

Cheers,

David


  Printer-friendly page | Top

 
Conferences | Topics | Previous Topic | Next Topic
David Ryan
unregistered user
Oct-22-03, 05:32 AM (PDT)
 
1. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #0
 
   Good news, bad news . . .

Found the old files (had renamed them, but forgot I had done it), but when I try to start now (clicking on icon on desktop) I get - <<Can't create server process with command line "Sawmill6CL.exe subordinate -ws t -mpi 170">>

Ideas ?

Will try sawmill6cl.exe by itself and see what happens.

Thanks,

David


  Printer-friendly page | Top
David Ryan
unregistered user
Oct-22-03, 05:37 AM (PDT)
 
2. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #1
 
   Better news, worse news . . .

Discovered the desktop link had magically changed destination (to new_sawmill.exe). Changed it back and now when 6.5.0 starts up I have *no* configs.

*Please* make the migration between versions smoother.

David


  Printer-friendly page | Top
David Ryan
unregistered user
Oct-22-03, 05:58 AM (PDT)
 
3. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #2
 
   I think the problem is that my old config file has been 6.5.3-ised and 6.5.0 doesn't like it anymore.

Unfortunately it looks like un-6.5.3-ising it is too long to do (assuming I could work out exactly which fields it doesn't like) so I may have to simply rebuild it from scratch.

How about creating a backup of configs *before* updating them ? I know I could have backed it up myself, but I would normally think of this when doing a major upgrade and I didn't reckon this was the case.

Cheers,

David


  Printer-friendly page | Top
ferraradmin
Member since Sep-5-01
3120 posts
Oct-23-03, 11:19 AM (PDT)
Click to EMail ferrar Click to send private message to ferrar Click to view user profileClick to add this user to your buddy list  
4. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #3
 
Hmm, lots of problems. Upgrades are usually much smoother than this-- the Windows installer locates the existing installation (where it was installed last time), and replaces Sawmill6CL.exe with the new version. That's the only file that needs to be replaced, so if you've installed somewhere else, you can update that installation by copying that file. It sounds like there might have been two installation locations on your system, and the installer updated the shortcuts to point to the *new* installation. This can happen if you install to a new location for the new installation, instead of putting it in the same directory where it was before. If this happens, you can copy Sawmill6CL.exe to the old installation, or copy LogAnalysisInfo to the new installation. An installation is really just Sawmill6CL.exe (which is Sawmill) and LogAnalysisInfo (which is Sawmill's data)-- as long as you pair the latest Sawmill6CL.exe with your LogAnalysisInfo, you should be okay.

The problem of auto-converting configurations is more serious. We're moving to a new configuration language in version 7 which should mostly solve this problem, because it won't have to know about every option it sees there-- it if doesn't recognize one, it will be able to just move on without generating an error, as v6 does. This should allow all but the most dramatic rewritings of a file to be "downgraded" and still work with a previous version. For now, however, it's wise to back up LogAnalysisInfo (just make a copy of the whole folder) before an upgrade, in case you run into problems like these.


  Printer-friendly page | Top
David Ryan
unregistered user
Oct-24-03, 07:40 AM (PDT)
 
5. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #4
 
   Greg,

Thanks for the reply.

I actually installed 6.5.3 on a different machine and copied those files over.

I'm still not exactly clear what the standard upgrade process is. Assume I have 6.5.0 installed and want to install 6.5.3 - do I run the installer to a new directory and then manually copy sawmill.exe and loganalysisinfo over, or do I simply run the installer and point it to the existing install directory and let it 6.5.3-ise my existing configuration file ?

Also, is there any way to provide a list of fields which have been added or modified between the two versions ? This would allow me to manually go in and remove the offending lines. I tried rebuilding the config from scratch, but I had forgotten how long it took me to build it. I think it would be quicker to un6.5.3ise the config than rebuild it.

Thanks,

David


  Printer-friendly page | Top
i21
Member since Mar-21-02
1719 posts
Oct-28-03, 01:31 AM (PDT)
Click to EMail i21 Click to view user profileClick to add this user to your buddy list  
6. "RE: sawmill6cl.exe going 100% even when I kill it"
In response to message #5
 
On a windows machine with 1 Sawmill installation (the default is c:\prgram files\sawmill) the installer will find that dir and upgrade it.

When there are two installations things are slightly more complex, all the new shortcuts Sawmill creates will be to the new install, so depending where you want the shortcuts to go or where they were going will depend on how you set the new install up.

I use many different set ups here for testing and I have found the simplest way to upgrade is to install Sawmill into the default location on C drive and move the sawmill6CL file across to my "real" running directory. Each time I upgrade I simply upgrade the C install.

The start menu short cuts and desktop icons will be pointing at the c:\ install all the time, I just delete the desktop icon and use my existing manually created shortcuts on the desktop to get to the install I need.

Hope this helps.

Graham
Technical Support

support@thesawmill.co.uk


  Printer-friendly page | Top

Conferences | Topics | Previous Topic | Next Topic
 
 
Home    Lite    Professional    Enterprise    Samples    FAQ    Downloads    Purchase    Manual    Support    Contact Us
Copyright © 2006 by Flowerfire. Privacy Policy