Hi,

I have a DBISam table  (version 3) that works fine in my application if I
use is on my local machine (Windows 7 64 bits). If I install the app on a
server (Windows 2008, 64 bits), I immediately  get the DBISam Engine Error #
8961 if I start the app and open the table (the table is a detail table).
When I use the RepairTable function, alle problems are solved and it works
fine.

The strange thing is that even if I do a RepairTable before installing, I
still get the error on the server. But if I call then RepairTable function
on the server, all errors disappear!

Has anybody seen this before?

Greetings,
Ronald

Ronald,

This has come up in the past and usually is due to something interfering
with the DBISAM so it reports headers corrupt.

- Does the repair actually detect and fix something ?

- Is the app and data in c:\Program Files (x86)\ ? If so then folder
visualization might play a role. Does the issue happen when you run it
somewhere else (e.g. c:\myapp)

- is Anti-virus installed and are your app folders excluded ?

- what's the OS locale info?  Should not really matter for this though.

Raul

On 7/31/2012 9:16 AM, Ronald wrote:
> Hi,
>
> I have a DBISam table  (version 3) that works fine in my application if
> I use is on my local machine (Windows 7 64 bits). If I install the app
> on a server (Windows 2008, 64 bits), I immediately  get the DBISam
> Engine Error # 8961 if I start the app and open the table (the table is
> a detail table). When I use the RepairTable function, alle problems are
> solved and it works fine.
>
> The strange thing is that even if I do a RepairTable before installing,
> I still get the error on the server. But if I call then RepairTable
> function on the server, all errors disappear!
>
> Has anybody seen this before?
>
> Greetings,
> Ronald
>
>

Hi Raul,

I do not know if the repair detects a problem. I do it in code (not with the
database system utility) and I do not let it report anything. I doubt if it
detects somthing. The table is only opened, nothing is written.
The folder is not in c:\program files (x86).
I will test the anti virus option.

Thanks,
Ronald

"Raul"  schreef in bericht
news:EC8311DB-DC71-49E4-94DF-CF1FF7CE43D1@news.elevatesoft.com...

Ronald,

This has come up in the past and usually is due to something interfering
with the DBISAM so it reports headers corrupt.

- Does the repair actually detect and fix something ?

- Is the app and data in c:\Program Files (x86)\ ? If so then folder
visualization might play a role. Does the issue happen when you run it
somewhere else (e.g. c:\myapp)

- is Anti-virus installed and are your app folders excluded ?

- what's the OS locale info?  Should not really matter for this though.

Raul

On 7/31/2012 9:16 AM, Ronald wrote:
> Hi,
>
> I have a DBISam table  (version 3) that works fine in my application if
> I use is on my local machine (Windows 7 64 bits). If I install the app
> on a server (Windows 2008, 64 bits), I immediately  get the DBISam
> Engine Error # 8961 if I start the app and open the table (the table is
> a detail table). When I use the RepairTable function, alle problems are
> solved and it works fine.
>
> The strange thing is that even if I do a RepairTable before installing,
> I still get the error on the server. But if I call then RepairTable
> function on the server, all errors disappear!
>
> Has anybody seen this before?
>
> Greetings,
> Ronald
>
>

There is no virusscanner running.

"Ronald"  schreef in bericht
news:FCE561AA-4A87-4867-BC1D-DEC9C9491ABD@news.elevatesoft.com...

Hi Raul,

I do not know if the repair detects a problem. I do it in code (not with the
database system utility) and I do not let it report anything. I doubt if it
detects somthing. The table is only opened, nothing is written.
The folder is not in c:\program files (x86).
I will test the anti virus option.

Thanks,
Ronald

"Raul"  schreef in bericht
news:EC8311DB-DC71-49E4-94DF-CF1FF7CE43D1@news.elevatesoft.com...

Ronald,

This has come up in the past and usually is due to something interfering
with the DBISAM so it reports headers corrupt.

- Does the repair actually detect and fix something ?

- Is the app and data in c:\Program Files (x86)\ ? If so then folder
visualization might play a role. Does the issue happen when you run it
somewhere else (e.g. c:\myapp)

- is Anti-virus installed and are your app folders excluded ?

- what's the OS locale info?  Should not really matter for this though.

Raul

On 7/31/2012 9:16 AM, Ronald wrote:
> Hi,
>
> I have a DBISam table  (version 3) that works fine in my application if
> I use is on my local machine (Windows 7 64 bits). If I install the app
> on a server (Windows 2008, 64 bits), I immediately  get the DBISam
> Engine Error # 8961 if I start the app and open the table (the table is
> a detail table). When I use the RepairTable function, alle problems are
> solved and it works fine.
>
> The strange thing is that even if I do a RepairTable before installing,
> I still get the error on the server. But if I call then RepairTable
> function on the server, all errors disappear!
>
> Has anybody seen this before?
>
> Greetings,
> Ronald
>
>

I checked the server, but there is no virusscanner running.

"Ronald"  schreef in bericht
news:FCE561AA-4A87-4867-BC1D-DEC9C9491ABD@news.elevatesoft.com...

Hi Raul,

I do not know if the repair detects a problem. I do it in code (not with the
database system utility) and I do not let it report anything. I doubt if it
detects somthing. The table is only opened, nothing is written.
The folder is not in c:\program files (x86).
I will test the anti virus option.

Thanks,
Ronald

"Raul"  schreef in bericht
news:EC8311DB-DC71-49E4-94DF-CF1FF7CE43D1@news.elevatesoft.com...

Ronald,

This has come up in the past and usually is due to something interfering
with the DBISAM so it reports headers corrupt.

- Does the repair actually detect and fix something ?

- Is the app and data in c:\Program Files (x86)\ ? If so then folder
visualization might play a role. Does the issue happen when you run it
somewhere else (e.g. c:\myapp)

- is Anti-virus installed and are your app folders excluded ?

- what's the OS locale info?  Should not really matter for this though.

Raul

On 7/31/2012 9:16 AM, Ronald wrote:
> Hi,
>
> I have a DBISam table  (version 3) that works fine in my application if
> I use is on my local machine (Windows 7 64 bits). If I install the app
> on a server (Windows 2008, 64 bits), I immediately  get the DBISam
> Engine Error # 8961 if I start the app and open the table (the table is
> a detail table). When I use the RepairTable function, alle problems are
> solved and it works fine.
>
> The strange thing is that even if I do a RepairTable before installing,
> I still get the error on the server. But if I call then RepairTable
> function on the server, all errors disappear!
>
> Has anybody seen this before?
>
> Greetings,
> Ronald
>
>

Ronald,

<< I have a DBISam table  (version 3) that works fine in my application if I
use is on my local machine (Windows 7 64 bits). If I install the app on a
server (Windows 2008, 64 bits), I immediately  get the DBISam Engine Error #
8961 if I start the app and open the table (the table is a detail table).
When I use the RepairTable function, alle problems are solved and it works
fine. >>

If you can, please send the table via email and I'll tell you what the
problem is if I can reproduce it here on our 2008 server.  Like Raul, I
suspect that the issue may be with the system locale.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

Ronald,

Thanks for the files.

The problem is that you've got a default expression of 1,3 in the table.  If
you try to open the table on a machine that doesn't use the comma as a
decimal separator, then you'll get this error because DBISAM thinks the
default expression is invalid.

This has all been changed in DBISAM 4, which uses ANSI decimal separators
and date/time formatting, so it hasn't been an issue for years.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks a lot, Tim,
I did not realize that this could cause the error. I will check it on the
server this week immediately.
Again, thanks a lot.

"Tim Young [Elevate Software]"  schreef in bericht
news:147ACA4C-6A06-4C0C-9EC0-578BC13838ED@news.elevatesoft.com...

Ronald,

Thanks for the files.

The problem is that you've got a default expression of 1,3 in the table.  If
you try to open the table on a machine that doesn't use the comma as a
decimal separator, then you'll get this error because DBISAM thinks the
default expression is invalid.

This has all been changed in DBISAM 4, which uses ANSI decimal separators
and date/time formatting, so it hasn't been an issue for years.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Your solution solved the problem!


"Ronald"  schreef in bericht
news:C2BDF31C-D330-4CA6-9AE6-CBC5AF3CE95B@news.elevatesoft.com...

Thanks a lot, Tim,
I did not realize that this could cause the error. I will check it on the
server this week immediately.
Again, thanks a lot.

"Tim Young [Elevate Software]"  schreef in bericht
news:147ACA4C-6A06-4C0C-9EC0-578BC13838ED@news.elevatesoft.com...

Ronald,

Thanks for the files.

The problem is that you've got a default expression of 1,3 in the table.  If
you try to open the table on a machine that doesn't use the comma as a
decimal separator, then you'll get this error because DBISAM thinks the
default expression is invalid.

This has all been changed in DBISAM 4, which uses ANSI decimal separators
and date/time formatting, so it hasn't been an issue for years.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com