Subject | RE: [firebird-support] Generators, what could cause resetting generator values to some earlier version |
---|---|
Author | bogdan |
Post date | 2012-08-07T18:18:07Z |
I would check the data.
It seems like an old version of database .
Copy, system restore ??
Regards, Bogdan
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Sofija Blazevski
Sent: Tuesday, August 07, 2012 4:07 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Generators, what could cause resetting generator
values to some earlier version
Hello,
I have a encountered a problem at client installation I've never had
before, I didn't even think it would be possible.
Server setup is Firebird 2.1.3 SuperServer on Windows Server 2008
Enterprise. Firebird is used on default port with no special setup.
Multiple users log on the server via RDP.
Problem is that generator values are changed (from nowhere) to some
earlier version say about 15 days ago, on the other side all of the data
is current.
Do you have any idea what could have caused an issue like this?
Could this be due to some windows issue? Same server had security.fdb
corrupted about a month ago.
Thanks,
- Sofija
[Non-text portions of this message have been removed]
It seems like an old version of database .
Copy, system restore ??
Regards, Bogdan
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Sofija Blazevski
Sent: Tuesday, August 07, 2012 4:07 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Generators, what could cause resetting generator
values to some earlier version
Hello,
I have a encountered a problem at client installation I've never had
before, I didn't even think it would be possible.
Server setup is Firebird 2.1.3 SuperServer on Windows Server 2008
Enterprise. Firebird is used on default port with no special setup.
Multiple users log on the server via RDP.
Problem is that generator values are changed (from nowhere) to some
earlier version say about 15 days ago, on the other side all of the data
is current.
Do you have any idea what could have caused an issue like this?
Could this be due to some windows issue? Same server had security.fdb
corrupted about a month ago.
Thanks,
- Sofija
[Non-text portions of this message have been removed]