Groups > Interbase > Interbase General discussion > Re: IB Stopped After Hard Drive Change




IB Stopped After Hard Drive Change

IB Stopped After Hard Drive Change
16 Apr 2008 15:24:26 -0700
I replaced my local hard drive with a new hard drive. Copied the entire
drive using  Western Digitals included utility. Worked surprisingly
well, reporting only 11 file errors - which it identified, mostly old
IE5 temp files.
Everything came right back up - except the IB Server. Even MS Sql
Server came up by itself.  Tried to start manually, and message changes
from Stopped to Started, but it doesn't seem to be started. The
connection tests don't seem to be responding normally.
Could the license mechanism be sensative to the drive hardware? IB
Server 7.51 Local Desktop. Windows XP.

-- 
Post Reply
Re: IB Stopped After Hard Drive Change
16 Apr 2008 16:41:50 -0700
Patrick Moloney wrote:

> Could the license mechanism be sensative to the drive hardware? IB
> Server 7.51 Local Desktop. Windows XP.

Yes. Try reregistering.

-- 
Post Reply
Re: IB Stopped After Hard Drive Change
17 Apr 2008 07:09:41 -0700
Bill Todd [TeamB] wrote:

> Yes. Try reregistering.

Yeah, that worked. I just didn't realize that the license was tied to
the hard-drive.
Any idea if that changed in IB2007?

Delphi didn't have a problem so that license must be different.

-- 
Post Reply
Re: IB Stopped After Hard Drive Change
17 Apr 2008 08:22:19 -0700
Patrick Moloney wrote:

> Yeah, that worked. I just didn't realize that the license was tied to
> the hard-drive.
> Any idea if that changed in IB2007?

I have no idea. I know virtually nothing about how Sanctuary works
other than that it node locks the software. I recall seeing a post from
someone at CodeGear stating that the hard disk serial number is part of
the node lock. That  is why I suggested reregistering. Perhaps Quinn or
someone else can provide a more complete answer.

-- 
Post Reply
Re: IB Stopped After Hard Drive Change
Thu, 17 Apr 2008 08:57:11 -070
The registration for InterBase keeps the volume label of your system 
drive (normally drive C). This prevents it from being copied from 
machine to machine, yet lets all users on the system use it. So, unless 
a new drive has the same volume label, InterBase must be re-registered. 
InterBase 7.5 and 2007 work the same here.

Bill Todd [TeamB] wrote:
> Patrick Moloney wrote:
> 
>> Yeah, that worked. I just didn't realize that the license was tied to
>> the hard-drive.
>> Any idea if that changed in IB2007?
> 
> I have no idea. I know virtually nothing about how Sanctuary works
> other than that it node locks the software. I recall seeing a post from
> someone at CodeGear stating that the hard disk serial number is part of
> the node lock. That  is why I suggested reregistering. Perhaps Quinn or
> someone else can provide a more complete answer.
Post Reply
<< Previous 1 2 Next >>
( Page 1 of 2 )
about | contact