Alaska Software Inc. - IDSC everywhere
Username: Password:
AuthorTopic: IDSC everywhere
Ott HavasvlgyiIDSC everywhere
on Sun, 06 Nov 2011 14:24:43 +0100
Hi,

Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
~12 users

With 1.82.306 I had problems.

I get quite strange IDSC errors quite often nowadays on one of my sites.
Earlier everything went fine there. Other sites with the same environments
have no such errors. Some sites has x64 Windows, and no such problems occur
there.

Here are some examples:


Xbase++ version     : Xbase++ (R) Version 1.82.294
Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
----------------------------------------------------------------------------
--
oError:args         :
oError:canDefault   : N
oError:canRetry     : N
oError:canSubstitute: N
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    :
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          1
oError:tries        :          0

The call was actually a standard AppEvent().



oError:args         :
          -> VALTYPE: O CLASS: XbpFont
          -> VALTYPE: C VALUE: 11.Arial CE
oError:canDefault   : N
oError:canRetry     : N
oError:canSubstitute: Y
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    : :Configure
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          1
oError:tries        :          0

This has been quite frequent for many weeks. And also XbpFont:create().



oError:args         :
          -> VALTYPE: O CLASS: XbpFont
oError:canDefault   : N
oError:canRetry     : N
oError:canSubstitute: Y
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    : :create
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          1
oError:tries        :          0

In this case the error log ended here, no callstack, so it happened during
error creation.



oError:args         :
          -> VALTYPE: C VALUE: username
oError:canDefault   : N
oError:canRetry     : N
oError:canSubstitute: Y
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    : getEnv
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          1
oError:tries        :          0

This happened also during error log creation. Username would be part of it.
This is a quite new kind of error.



oError:args         :
          -> VALTYPE: U VALUE: NIL
          -> VALTYPE: U VALUE: NIL
          -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
          -> VALTYPE: U VALUE: NIL
          -> VALTYPE: L VALUE: .F.
oError:canDefault   : Y
oError:canRetry     : Y
oError:canSubstitute: N
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    : DbUseArea
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          1
oError:tries        :          1

This is an exclusive open dbf.


And so on...  


These are quite unususal errors IMO, and the customer is quite unsatisfied
because of it. They happens almost every day.
1. What do you think the cause can be of this?
2. What is responsible for an IDSC at all?
3. When exactly does Xbase++ report such error?
4. What does become corrupted?
5. Can RAM error cause this?

Thanks in advance for your help,
Otto
James Loughner Re: IDSC everywhere
on Sun, 06 Nov 2011 13:10:58 -0500
Could be a RAM error. Also might be out of memory. Could also be a usage 
pattern. The people at the one site are doing something odd.
Also may be a error caused buy an external program like a Virus checker.

Is this seen on a single machine or multiple machines on a network?

Jim


On 11/06/2011 08:24 AM, Ottó Havasvölgyi wrote:
> Hi,
>
> Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
> ~12 users
>
> With 1.82.306 I had problems.
>
> I get quite strange IDSC errors quite often nowadays on one of my sites.
> Earlier everything went fine there. Other sites with the same environments
> have no such errors. Some sites has x64 Windows, and no such problems occur
> there.
>
> Here are some examples:
>
>
> Xbase++ version     : Xbase++ (R) Version 1.82.294
> Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
> ----------------------------------------------------------------------------
> --
> oError:args         :
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    :
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> The call was actually a standard AppEvent().
>
>
>
> oError:args         :
>            ->  VALTYPE: O CLASS: XbpFont
>            ->  VALTYPE: C VALUE: 11.Arial CE
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :Configure
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This has been quite frequent for many weeks. And also XbpFont:create().
>
>
>
> oError:args         :
>            ->  VALTYPE: O CLASS: XbpFont
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :create
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> In this case the error log ended here, no callstack, so it happened during
> error creation.
>
>
>
> oError:args         :
>            ->  VALTYPE: C VALUE: username
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : getEnv
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This happened also during error log creation. Username would be part of it.
> This is a quite new kind of error.
>
>
>
> oError:args         :
>            ->  VALTYPE: U VALUE: NIL
>            ->  VALTYPE: U VALUE: NIL
>            ->  VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>            ->  VALTYPE: U VALUE: NIL
>            ->  VALTYPE: L VALUE: .F.
> oError:canDefault   : Y
> oError:canRetry     : Y
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : DbUseArea
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          1
>
> This is an exclusive open dbf.
>
>
> And so on...  
>
>
> These are quite unususal errors IMO, and the customer is quite unsatisfied
> because of it. They happens almost every day.
> 1. What do you think the cause can be of this?
> 2. What is responsible for an IDSC at all?
> 3. When exactly does Xbase++ report such error?
> 4. What does become corrupted?
> 5. Can RAM error cause this?
>
> Thanks in advance for your help,
> Otto
>
>
Rvveelen Re: IDSC everywhere
on Mon, 07 Nov 2011 09:21:49 +0100
Op Sun, 06 Nov 2011 13:10:58 -0500 schreef James Loughner:

> Could be a RAM error. Also might be out of memory. Could also be a usage 
> pattern. The people at the one site are doing something odd.
> Also may be a error caused buy an external program like a Virus checker.
> 
> Is this seen on a single machine or multiple machines on a network?
> 
> Jim
> 
> 
> On 11/06/2011 08:24 AM, Ottó Havasvölgyi wrote:
>> Hi,
>>
>> Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
>> ~12 users
>>
>> With 1.82.306 I had problems.
>>
>> I get quite strange IDSC errors quite often nowadays on one of my sites.
>> Earlier everything went fine there. Other sites with the same environments
>> have no such errors. Some sites has x64 Windows, and no such problems occur
>> there.
>>
>> Here are some examples:
>>
>>
>> Xbase++ version     : Xbase++ (R) Version 1.82.294
>> Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
>> ----------------------------------------------------------------------------
>> --
>> oError:args         :
>> oError:canDefault   : N
>> oError:canRetry     : N
>> oError:canSubstitute: N
>> oError:cargo        : NIL
>> oError:description  : Internal data structures corrupted
>> oError:filename     :
>> oError:genCode      :         41
>> oError:operation    :
>> oError:osCode       :          0
>> oError:severity     :          2
>> oError:subCode      :          5
>> oError:subSystem    : BASE
>> oError:thread       :          1
>> oError:tries        :          0
>>
>> The call was actually a standard AppEvent().
>>
>>
>>
>> oError:args         :
>>            ->  VALTYPE: O CLASS: XbpFont
>>            ->  VALTYPE: C VALUE: 11.Arial CE
>> oError:canDefault   : N
>> oError:canRetry     : N
>> oError:canSubstitute: Y
>> oError:cargo        : NIL
>> oError:description  : Internal data structures corrupted
>> oError:filename     :
>> oError:genCode      :         41
>> oError:operation    : :Configure
>> oError:osCode       :          0
>> oError:severity     :          2
>> oError:subCode      :          5
>> oError:subSystem    : BASE
>> oError:thread       :          1
>> oError:tries        :          0
>>
>> This has been quite frequent for many weeks. And also XbpFont:create().
>>
>>
>>
>> oError:args         :
>>            ->  VALTYPE: O CLASS: XbpFont
>> oError:canDefault   : N
>> oError:canRetry     : N
>> oError:canSubstitute: Y
>> oError:cargo        : NIL
>> oError:description  : Internal data structures corrupted
>> oError:filename     :
>> oError:genCode      :         41
>> oError:operation    : :create
>> oError:osCode       :          0
>> oError:severity     :          2
>> oError:subCode      :          5
>> oError:subSystem    : BASE
>> oError:thread       :          1
>> oError:tries        :          0
>>
>> In this case the error log ended here, no callstack, so it happened during
>> error creation.
>>
>>
>>
>> oError:args         :
>>            ->  VALTYPE: C VALUE: username
>> oError:canDefault   : N
>> oError:canRetry     : N
>> oError:canSubstitute: Y
>> oError:cargo        : NIL
>> oError:description  : Internal data structures corrupted
>> oError:filename     :
>> oError:genCode      :         41
>> oError:operation    : getEnv
>> oError:osCode       :          0
>> oError:severity     :          2
>> oError:subCode      :          5
>> oError:subSystem    : BASE
>> oError:thread       :          1
>> oError:tries        :          0
>>
>> This happened also during error log creation. Username would be part of it.
>> This is a quite new kind of error.
>>
>>
>>
>> oError:args         :
>>            ->  VALTYPE: U VALUE: NIL
>>            ->  VALTYPE: U VALUE: NIL
>>            ->  VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>>            ->  VALTYPE: U VALUE: NIL
>>            ->  VALTYPE: L VALUE: .F.
>> oError:canDefault   : Y
>> oError:canRetry     : Y
>> oError:canSubstitute: N
>> oError:cargo        : NIL
>> oError:description  : Internal data structures corrupted
>> oError:filename     :
>> oError:genCode      :         41
>> oError:operation    : DbUseArea
>> oError:osCode       :          0
>> oError:severity     :          2
>> oError:subCode      :          5
>> oError:subSystem    : BASE
>> oError:thread       :          1
>> oError:tries        :          1
>>
>> This is an exclusive open dbf.
>>
>>
>> And so on...  
>>
>>
>> These are quite unususal errors IMO, and the customer is quite unsatisfied
>> because of it. They happens almost every day.
>> 1. What do you think the cause can be of this?
>> 2. What is responsible for an IDSC at all?
>> 3. When exactly does Xbase++ report such error?
>> 4. What does become corrupted?
>> 5. Can RAM error cause this?
>>
>> Thanks in advance for your help,
>> Otto
>>
>>

Hi,

We are struggling with a similar sort of issue. Using processmonitor
(Alaska pointed me in that direction) I found a NETWORK ERROR while reading
a DLL. Maybe you could check the same? The thing is we run our application
(in most cases) from a file server on several terminal servers. So data,
DLL's and EXE's are all on the file server. And the clients start the app
from the terminal server.

One of the solutions was to change that and leave the data on the file
server and move the DLL's and EXE's to the terminal servers. But now I have
an update issue .
Another solution was to change the autodisconnect parameters of the OS,
because the mapping gets disconnected after a while and in the wrong kind
of circumstances that causes errors when the DLL is tried to be read on the
file server.

Hope this helps you in the right direction! Good luck!

Best regards,
Ronald van Veelen
James Loughner Re: IDSC everywhere
on Mon, 07 Nov 2011 14:39:53 -0500
An other thought I have seen IDSC from corrupted indexes.

Jim

On 11/07/2011 03:21 AM, Rvveelen wrote:
> Op Sun, 06 Nov 2011 13:10:58 -0500 schreef James Loughner:
>
>> Could be a RAM error. Also might be out of memory. Could also be a usage
>> pattern. The people at the one site are doing something odd.
>> Also may be a error caused buy an external program like a Virus checker.
>>
>> Is this seen on a single machine or multiple machines on a network?
>>
>> Jim
>>
>>
>> On 11/06/2011 08:24 AM, Ottó Havasvölgyi wrote:
>>> Hi,
>>>
>>> Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
>>> ~12 users
>>>
>>> With 1.82.306 I had problems.
>>>
>>> I get quite strange IDSC errors quite often nowadays on one of my sites.
>>> Earlier everything went fine there. Other sites with the same environments
>>> have no such errors. Some sites has x64 Windows, and no such problems occur
>>> there.
>>>
>>> Here are some examples:
>>>
>>>
>>> Xbase++ version     : Xbase++ (R) Version 1.82.294
>>> Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
>>> ----------------------------------------------------------------------------
>>> --
>>> oError:args         :
>>> oError:canDefault   : N
>>> oError:canRetry     : N
>>> oError:canSubstitute: N
>>> oError:cargo        : NIL
>>> oError:description  : Internal data structures corrupted
>>> oError:filename     :
>>> oError:genCode      :         41
>>> oError:operation    :
>>> oError:osCode       :          0
>>> oError:severity     :          2
>>> oError:subCode      :          5
>>> oError:subSystem    : BASE
>>> oError:thread       :          1
>>> oError:tries        :          0
>>>
>>> The call was actually a standard AppEvent().
>>>
>>>
>>>
>>> oError:args         :
>>>             ->   VALTYPE: O CLASS: XbpFont
>>>             ->   VALTYPE: C VALUE: 11.Arial CE
>>> oError:canDefault   : N
>>> oError:canRetry     : N
>>> oError:canSubstitute: Y
>>> oError:cargo        : NIL
>>> oError:description  : Internal data structures corrupted
>>> oError:filename     :
>>> oError:genCode      :         41
>>> oError:operation    : :Configure
>>> oError:osCode       :          0
>>> oError:severity     :          2
>>> oError:subCode      :          5
>>> oError:subSystem    : BASE
>>> oError:thread       :          1
>>> oError:tries        :          0
>>>
>>> This has been quite frequent for many weeks. And also XbpFont:create().
>>>
>>>
>>>
>>> oError:args         :
>>>             ->   VALTYPE: O CLASS: XbpFont
>>> oError:canDefault   : N
>>> oError:canRetry     : N
>>> oError:canSubstitute: Y
>>> oError:cargo        : NIL
>>> oError:description  : Internal data structures corrupted
>>> oError:filename     :
>>> oError:genCode      :         41
>>> oError:operation    : :create
>>> oError:osCode       :          0
>>> oError:severity     :          2
>>> oError:subCode      :          5
>>> oError:subSystem    : BASE
>>> oError:thread       :          1
>>> oError:tries        :          0
>>>
>>> In this case the error log ended here, no callstack, so it happened during
>>> error creation.
>>>
>>>
>>>
>>> oError:args         :
>>>             ->   VALTYPE: C VALUE: username
>>> oError:canDefault   : N
>>> oError:canRetry     : N
>>> oError:canSubstitute: Y
>>> oError:cargo        : NIL
>>> oError:description  : Internal data structures corrupted
>>> oError:filename     :
>>> oError:genCode      :         41
>>> oError:operation    : getEnv
>>> oError:osCode       :          0
>>> oError:severity     :          2
>>> oError:subCode      :          5
>>> oError:subSystem    : BASE
>>> oError:thread       :          1
>>> oError:tries        :          0
>>>
>>> This happened also during error log creation. Username would be part of it.
>>> This is a quite new kind of error.
>>>
>>>
>>>
>>> oError:args         :
>>>             ->   VALTYPE: U VALUE: NIL
>>>             ->   VALTYPE: U VALUE: NIL
>>>             ->   VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>>>             ->   VALTYPE: U VALUE: NIL
>>>             ->   VALTYPE: L VALUE: .F.
>>> oError:canDefault   : Y
>>> oError:canRetry     : Y
>>> oError:canSubstitute: N
>>> oError:cargo        : NIL
>>> oError:description  : Internal data structures corrupted
>>> oError:filename     :
>>> oError:genCode      :         41
>>> oError:operation    : DbUseArea
>>> oError:osCode       :          0
>>> oError:severity     :          2
>>> oError:subCode      :          5
>>> oError:subSystem    : BASE
>>> oError:thread       :          1
>>> oError:tries        :          1
>>>
>>> This is an exclusive open dbf.
>>>
>>>
>>> And so on...  
>>>
>>>
>>> These are quite unususal errors IMO, and the customer is quite unsatisfied
>>> because of it. They happens almost every day.
>>> 1. What do you think the cause can be of this?
>>> 2. What is responsible for an IDSC at all?
>>> 3. When exactly does Xbase++ report such error?
>>> 4. What does become corrupted?
>>> 5. Can RAM error cause this?
>>>
>>> Thanks in advance for your help,
>>> Otto
>>>
>>>
>
> Hi,
>
> We are struggling with a similar sort of issue. Using processmonitor
> (Alaska pointed me in that direction) I found a NETWORK ERROR while reading
> a DLL. Maybe you could check the same? The thing is we run our application
> (in most cases) from a file server on several terminal servers. So data,
> DLL's and EXE's are all on the file server. And the clients start the app
> from the terminal server.
>
> One of the solutions was to change that and leave the data on the file
> server and move the DLL's and EXE's to the terminal servers. But now I have
> an update issue .
> Another solution was to change the autodisconnect parameters of the OS,
> because the mapping gets disconnected after a while and in the wrong kind
> of circumstances that causes errors when the DLL is tried to be read on the
> file server.
>
> Hope this helps you in the right direction! Good luck!
>
> Best regards,
> Ronald van Veelen
Pascal BoivinRe: IDSC everywhere
on Mon, 07 Nov 2011 22:30:33 +0100
Hi

It happens quite often for a customers using Terminal Service and an
xbase app that create/destroy many fonts.  Now instead of creating them
for every windows, we create them once at the begining of the
application, and store the objects in a PUBLIC array.

aAdd(GlobalFont, { "Arial 11", oFont })


Almost all IDSC disappears after doing that change.
Ott HavasvlgyiRe: IDSC everywhere
on Wed, 09 Nov 2011 20:07:55 +0100
Thank you for your responses.

In my case this site has a Win2003, and all users work on it in a Remote
Desktop session. Data and executables are all on this server, so network
issues cannot be a problem here.
The application has been operating there for about 5 years.
The first 3 years was quite fine, no strange errors.
After that an also interesting error appeared: Bold fonts were not visible
when printed to any printer from any application and stay so until the
server was restarted. After doing that, it occured again after 8-10 days. So
the server had to be restarted again...   After a while it did not occur
more. Perhaps the admin did something.
After about 0.5-1 years the IDSC appeared, I described in my first post.

Sometimes the app crashes at startup at the first font creation.
It also can crash with IDSC with XbpDialog:create() operation.

Thanks,
Otto


"Ott Havasvlgyi" <vil@chello.hu> az albbiakat rta a kvetkezo zenetben
news:165d8800$1c5add33$1a71@news.alaska-software.com...
> Hi,
>
> Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
> ~12 users
>
> With 1.82.306 I had problems.
>
> I get quite strange IDSC errors quite often nowadays on one of my sites.
> Earlier everything went fine there. Other sites with the same environments
> have no such errors. Some sites has x64 Windows, and no such problems
occur
> there.
>
> Here are some examples:
>
>
> Xbase++ version     : Xbase++ (R) Version 1.82.294
> Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
> --------------------------------------------------------------------------
--
> --
> oError:args         :
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    :
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> The call was actually a standard AppEvent().
>
>
>
> oError:args         :
>           -> VALTYPE: O CLASS: XbpFont
>           -> VALTYPE: C VALUE: 11.Arial CE
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :Configure
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This has been quite frequent for many weeks. And also XbpFont:create().
>
>
>
> oError:args         :
>           -> VALTYPE: O CLASS: XbpFont
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :create
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> In this case the error log ended here, no callstack, so it happened during
> error creation.
>
>
>
> oError:args         :
>           -> VALTYPE: C VALUE: username
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : getEnv
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This happened also during error log creation. Username would be part of
it.
> This is a quite new kind of error.
>
>
>
> oError:args         :
>           -> VALTYPE: U VALUE: NIL
>           -> VALTYPE: U VALUE: NIL
>           -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>           -> VALTYPE: U VALUE: NIL
>           -> VALTYPE: L VALUE: .F.
> oError:canDefault   : Y
> oError:canRetry     : Y
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : DbUseArea
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          1
>
> This is an exclusive open dbf.
>
>
> And so on...  
>
>
> These are quite unususal errors IMO, and the customer is quite unsatisfied
> because of it. They happens almost every day.
> 1. What do you think the cause can be of this?
> 2. What is responsible for an IDSC at all?
> 3. When exactly does Xbase++ report such error?
> 4. What does become corrupted?
> 5. Can RAM error cause this?
>
> Thanks in advance for your help,
> Otto
>
>
Michael HoffmannRe: IDSC everywhere
on Sat, 12 Nov 2011 18:52:43 +0100
Hello Otto,
have you tried running your application on the TS with administrator 
privileges?
Best regards,
Michael


"Ott Havasvlgyi" <vil@chello.hu> wrote in message 
news:165d8800$1c5add33$1a71@news.alaska-software.com...
> Hi,
>
> Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++ 1.82.294;
> ~12 users
>
> With 1.82.306 I had problems.
>
> I get quite strange IDSC errors quite often nowadays on one of my sites.
> Earlier everything went fine there. Other sites with the same environments
> have no such errors. Some sites has x64 Windows, and no such problems 
> occur
> there.
>
> Here are some examples:
>
>
> Xbase++ version     : Xbase++ (R) Version 1.82.294
> Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
> ----------------------------------------------------------------------------
> --
> oError:args         :
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    :
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> The call was actually a standard AppEvent().
>
>
>
> oError:args         :
>          -> VALTYPE: O CLASS: XbpFont
>          -> VALTYPE: C VALUE: 11.Arial CE
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :Configure
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This has been quite frequent for many weeks. And also XbpFont:create().
>
>
>
> oError:args         :
>          -> VALTYPE: O CLASS: XbpFont
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : :create
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> In this case the error log ended here, no callstack, so it happened during
> error creation.
>
>
>
> oError:args         :
>          -> VALTYPE: C VALUE: username
> oError:canDefault   : N
> oError:canRetry     : N
> oError:canSubstitute: Y
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : getEnv
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          0
>
> This happened also during error log creation. Username would be part of 
> it.
> This is a quite new kind of error.
>
>
>
> oError:args         :
>          -> VALTYPE: U VALUE: NIL
>          -> VALTYPE: U VALUE: NIL
>          -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>          -> VALTYPE: U VALUE: NIL
>          -> VALTYPE: L VALUE: .F.
> oError:canDefault   : Y
> oError:canRetry     : Y
> oError:canSubstitute: N
> oError:cargo        : NIL
> oError:description  : Internal data structures corrupted
> oError:filename     :
> oError:genCode      :         41
> oError:operation    : DbUseArea
> oError:osCode       :          0
> oError:severity     :          2
> oError:subCode      :          5
> oError:subSystem    : BASE
> oError:thread       :          1
> oError:tries        :          1
>
> This is an exclusive open dbf.
>
>
> And so on...  
>
>
> These are quite unususal errors IMO, and the customer is quite unsatisfied
> because of it. They happens almost every day.
> 1. What do you think the cause can be of this?
> 2. What is responsible for an IDSC at all?
> 3. When exactly does Xbase++ report such error?
> 4. What does become corrupted?
> 5. Can RAM error cause this?
>
> Thanks in advance for your help,
> Otto
>
>
Ott HavasvlgyiRe: IDSC everywhere
on Tue, 15 Nov 2011 20:01:12 +0100
Hello,

Yes, I have, and the problem occured in that case too. What's more, perhaps
even more frequently than with a normal user.

Best regards,
Otto


<Michael Hoffmann> az albbiakat rta a kvetkezo zenetben
news:5b070f12$3ac9f404$12f63f@news.alaska-software.com...
> Hello Otto,
> have you tried running your application on the TS with administrator
> privileges?
> Best regards,
> Michael
>
>
> "Ott Havasvlgyi" <vil@chello.hu> wrote in message
> news:165d8800$1c5add33$1a71@news.alaska-software.com...
> > Hi,
> >
> > Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++
1.82.294;
> > ~12 users
> >
> > With 1.82.306 I had problems.
> >
> > I get quite strange IDSC errors quite often nowadays on one of my sites.
> > Earlier everything went fine there. Other sites with the same
environments
> > have no such errors. Some sites has x64 Windows, and no such problems
> > occur
> > there.
> >
> > Here are some examples:
> >
> >
> > Xbase++ version     : Xbase++ (R) Version 1.82.294
> > Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
>
> --------------------------------------------------------------------------
--
> > --
> > oError:args         :
> > oError:canDefault   : N
> > oError:canRetry     : N
> > oError:canSubstitute: N
> > oError:cargo        : NIL
> > oError:description  : Internal data structures corrupted
> > oError:filename     :
> > oError:genCode      :         41
> > oError:operation    :
> > oError:osCode       :          0
> > oError:severity     :          2
> > oError:subCode      :          5
> > oError:subSystem    : BASE
> > oError:thread       :          1
> > oError:tries        :          0
> >
> > The call was actually a standard AppEvent().
> >
> >
> >
> > oError:args         :
> >          -> VALTYPE: O CLASS: XbpFont
> >          -> VALTYPE: C VALUE: 11.Arial CE
> > oError:canDefault   : N
> > oError:canRetry     : N
> > oError:canSubstitute: Y
> > oError:cargo        : NIL
> > oError:description  : Internal data structures corrupted
> > oError:filename     :
> > oError:genCode      :         41
> > oError:operation    : :Configure
> > oError:osCode       :          0
> > oError:severity     :          2
> > oError:subCode      :          5
> > oError:subSystem    : BASE
> > oError:thread       :          1
> > oError:tries        :          0
> >
> > This has been quite frequent for many weeks. And also XbpFont:create().
> >
> >
> >
> > oError:args         :
> >          -> VALTYPE: O CLASS: XbpFont
> > oError:canDefault   : N
> > oError:canRetry     : N
> > oError:canSubstitute: Y
> > oError:cargo        : NIL
> > oError:description  : Internal data structures corrupted
> > oError:filename     :
> > oError:genCode      :         41
> > oError:operation    : :create
> > oError:osCode       :          0
> > oError:severity     :          2
> > oError:subCode      :          5
> > oError:subSystem    : BASE
> > oError:thread       :          1
> > oError:tries        :          0
> >
> > In this case the error log ended here, no callstack, so it happened
during
> > error creation.
> >
> >
> >
> > oError:args         :
> >          -> VALTYPE: C VALUE: username
> > oError:canDefault   : N
> > oError:canRetry     : N
> > oError:canSubstitute: Y
> > oError:cargo        : NIL
> > oError:description  : Internal data structures corrupted
> > oError:filename     :
> > oError:genCode      :         41
> > oError:operation    : getEnv
> > oError:osCode       :          0
> > oError:severity     :          2
> > oError:subCode      :          5
> > oError:subSystem    : BASE
> > oError:thread       :          1
> > oError:tries        :          0
> >
> > This happened also during error log creation. Username would be part of
> > it.
> > This is a quite new kind of error.
> >
> >
> >
> > oError:args         :
> >          -> VALTYPE: U VALUE: NIL
> >          -> VALTYPE: U VALUE: NIL
> >          -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
> >          -> VALTYPE: U VALUE: NIL
> >          -> VALTYPE: L VALUE: .F.
> > oError:canDefault   : Y
> > oError:canRetry     : Y
> > oError:canSubstitute: N
> > oError:cargo        : NIL
> > oError:description  : Internal data structures corrupted
> > oError:filename     :
> > oError:genCode      :         41
> > oError:operation    : DbUseArea
> > oError:osCode       :          0
> > oError:severity     :          2
> > oError:subCode      :          5
> > oError:subSystem    : BASE
> > oError:thread       :          1
> > oError:tries        :          1
> >
> > This is an exclusive open dbf.
> >
> >
> > And so on...  
> >
> >
> > These are quite unususal errors IMO, and the customer is quite
unsatisfied
> > because of it. They happens almost every day.
> > 1. What do you think the cause can be of this?
> > 2. What is responsible for an IDSC at all?
> > 3. When exactly does Xbase++ report such error?
> > 4. What does become corrupted?
> > 5. Can RAM error cause this?
> >
> > Thanks in advance for your help,
> > Otto
> >
> >
>
>
Michael HoffmannRe: IDSC everywhere
on Wed, 16 Nov 2011 08:07:01 +0100
Hello Otto,
have you tried process explorer to check out all dlls loaded into your 
process? Maybe some odd dll is hooking system calls and induces these 
errors.
HTH
Michael

"Ott Havasvlgyi" <vil@chello.hu> wrote in message 
news:66a85998$1e107489$dc52c@news.alaska-software.com...
> Hello,
>
> Yes, I have, and the problem occured in that case too. What's more, 
> perhaps
> even more frequently than with a normal user.
>
> Best regards,
> Otto
>
>
> <Michael Hoffmann> az albbiakat rta a kvetkezo zenetben
> news:5b070f12$3ac9f404$12f63f@news.alaska-software.com...
>> Hello Otto,
>> have you tried running your application on the TS with administrator
>> privileges?
>> Best regards,
>> Michael
>>
>>
>> "Ott Havasvlgyi" <vil@chello.hu> wrote in message
>> news:165d8800$1c5add33$1a71@news.alaska-software.com...
>> > Hi,
>> >
>> > Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++
> 1.82.294;
>> > ~12 users
>> >
>> > With 1.82.306 I had problems.
>> >
>> > I get quite strange IDSC errors quite often nowadays on one of my 
>> > sites.
>> > Earlier everything went fine there. Other sites with the same
> environments
>> > have no such errors. Some sites has x64 Windows, and no such problems
>> > occur
>> > there.
>> >
>> > Here are some examples:
>> >
>> >
>> > Xbase++ version     : Xbase++ (R) Version 1.82.294
>> > Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
>>
>> --------------------------------------------------------------------------
> --
>> > --
>> > oError:args         :
>> > oError:canDefault   : N
>> > oError:canRetry     : N
>> > oError:canSubstitute: N
>> > oError:cargo        : NIL
>> > oError:description  : Internal data structures corrupted
>> > oError:filename     :
>> > oError:genCode      :         41
>> > oError:operation    :
>> > oError:osCode       :          0
>> > oError:severity     :          2
>> > oError:subCode      :          5
>> > oError:subSystem    : BASE
>> > oError:thread       :          1
>> > oError:tries        :          0
>> >
>> > The call was actually a standard AppEvent().
>> >
>> >
>> >
>> > oError:args         :
>> >          -> VALTYPE: O CLASS: XbpFont
>> >          -> VALTYPE: C VALUE: 11.Arial CE
>> > oError:canDefault   : N
>> > oError:canRetry     : N
>> > oError:canSubstitute: Y
>> > oError:cargo        : NIL
>> > oError:description  : Internal data structures corrupted
>> > oError:filename     :
>> > oError:genCode      :         41
>> > oError:operation    : :Configure
>> > oError:osCode       :          0
>> > oError:severity     :          2
>> > oError:subCode      :          5
>> > oError:subSystem    : BASE
>> > oError:thread       :          1
>> > oError:tries        :          0
>> >
>> > This has been quite frequent for many weeks. And also XbpFont:create().
>> >
>> >
>> >
>> > oError:args         :
>> >          -> VALTYPE: O CLASS: XbpFont
>> > oError:canDefault   : N
>> > oError:canRetry     : N
>> > oError:canSubstitute: Y
>> > oError:cargo        : NIL
>> > oError:description  : Internal data structures corrupted
>> > oError:filename     :
>> > oError:genCode      :         41
>> > oError:operation    : :create
>> > oError:osCode       :          0
>> > oError:severity     :          2
>> > oError:subCode      :          5
>> > oError:subSystem    : BASE
>> > oError:thread       :          1
>> > oError:tries        :          0
>> >
>> > In this case the error log ended here, no callstack, so it happened
> during
>> > error creation.
>> >
>> >
>> >
>> > oError:args         :
>> >          -> VALTYPE: C VALUE: username
>> > oError:canDefault   : N
>> > oError:canRetry     : N
>> > oError:canSubstitute: Y
>> > oError:cargo        : NIL
>> > oError:description  : Internal data structures corrupted
>> > oError:filename     :
>> > oError:genCode      :         41
>> > oError:operation    : getEnv
>> > oError:osCode       :          0
>> > oError:severity     :          2
>> > oError:subCode      :          5
>> > oError:subSystem    : BASE
>> > oError:thread       :          1
>> > oError:tries        :          0
>> >
>> > This happened also during error log creation. Username would be part of
>> > it.
>> > This is a quite new kind of error.
>> >
>> >
>> >
>> > oError:args         :
>> >          -> VALTYPE: U VALUE: NIL
>> >          -> VALTYPE: U VALUE: NIL
>> >          -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
>> >          -> VALTYPE: U VALUE: NIL
>> >          -> VALTYPE: L VALUE: .F.
>> > oError:canDefault   : Y
>> > oError:canRetry     : Y
>> > oError:canSubstitute: N
>> > oError:cargo        : NIL
>> > oError:description  : Internal data structures corrupted
>> > oError:filename     :
>> > oError:genCode      :         41
>> > oError:operation    : DbUseArea
>> > oError:osCode       :          0
>> > oError:severity     :          2
>> > oError:subCode      :          5
>> > oError:subSystem    : BASE
>> > oError:thread       :          1
>> > oError:tries        :          1
>> >
>> > This is an exclusive open dbf.
>> >
>> >
>> > And so on...  
>> >
>> >
>> > These are quite unususal errors IMO, and the customer is quite
> unsatisfied
>> > because of it. They happens almost every day.
>> > 1. What do you think the cause can be of this?
>> > 2. What is responsible for an IDSC at all?
>> > 3. When exactly does Xbase++ report such error?
>> > 4. What does become corrupted?
>> > 5. Can RAM error cause this?
>> >
>> > Thanks in advance for your help,
>> > Otto
>> >
>> >
>>
>>
>
>
Ott HavasvlgyiRe: IDSC everywhere
on Sat, 19 Nov 2011 19:42:21 +0100
Hello,

Thanks for your idea.
I have checked it out, but did not see any unusual dll. Lots of Microsoft
dlls, Alaska dlls, some FinePrint and HP dlls, and our own binaries. But
maybe I should look at this when the IDSC happens. But strangely there have
not been any IDSCs since 5th of November, although we haven't done anything
with the server and application.

Best regards,
Otto


<Michael Hoffmann> az albbiakat rta a kvetkezo zenetben
news:5438d073$39b4416d$139806@news.alaska-software.com...
> Hello Otto,
> have you tried process explorer to check out all dlls loaded into your
> process? Maybe some odd dll is hooking system calls and induces these
> errors.
> HTH
> Michael
>
> "Ott Havasvlgyi" <vil@chello.hu> wrote in message
> news:66a85998$1e107489$dc52c@news.alaska-software.com...
> > Hello,
> >
> > Yes, I have, and the problem occured in that case too. What's more,
> > perhaps
> > even more frequently than with a normal user.
> >
> > Best regards,
> > Otto
> >
> >
> > <Michael Hoffmann> az albbiakat rta a kvetkezo zenetben
> > news:5b070f12$3ac9f404$12f63f@news.alaska-software.com...
> >> Hello Otto,
> >> have you tried running your application on the TS with administrator
> >> privileges?
> >> Best regards,
> >> Michael
> >>
> >>
> >> "Ott Havasvlgyi" <vil@chello.hu> wrote in message
> >> news:165d8800$1c5add33$1a71@news.alaska-software.com...
> >> > Hi,
> >> >
> >> > Environment: x86, Win2003 R2 SP2 with Terminal Services; Xbase++
> > 1.82.294;
> >> > ~12 users
> >> >
> >> > With 1.82.306 I had problems.
> >> >
> >> > I get quite strange IDSC errors quite often nowadays on one of my
> >> > sites.
> >> > Earlier everything went fine there. Other sites with the same
> > environments
> >> > have no such errors. Some sites has x64 Windows, and no such problems
> >> > occur
> >> > there.
> >> >
> >> > Here are some examples:
> >> >
> >> >
> >> > Xbase++ version     : Xbase++ (R) Version 1.82.294
> >> > Operating system    : Windows XP 05.02 Build 03790 Szervizcsomag 2
> >>
>
>> -------------------------------------------------------------------------
-
> > --
> >> > --
> >> > oError:args         :
> >> > oError:canDefault   : N
> >> > oError:canRetry     : N
> >> > oError:canSubstitute: N
> >> > oError:cargo        : NIL
> >> > oError:description  : Internal data structures corrupted
> >> > oError:filename     :
> >> > oError:genCode      :         41
> >> > oError:operation    :
> >> > oError:osCode       :          0
> >> > oError:severity     :          2
> >> > oError:subCode      :          5
> >> > oError:subSystem    : BASE
> >> > oError:thread       :          1
> >> > oError:tries        :          0
> >> >
> >> > The call was actually a standard AppEvent().
> >> >
> >> >
> >> >
> >> > oError:args         :
> >> >          -> VALTYPE: O CLASS: XbpFont
> >> >          -> VALTYPE: C VALUE: 11.Arial CE
> >> > oError:canDefault   : N
> >> > oError:canRetry     : N
> >> > oError:canSubstitute: Y
> >> > oError:cargo        : NIL
> >> > oError:description  : Internal data structures corrupted
> >> > oError:filename     :
> >> > oError:genCode      :         41
> >> > oError:operation    : :Configure
> >> > oError:osCode       :          0
> >> > oError:severity     :          2
> >> > oError:subCode      :          5
> >> > oError:subSystem    : BASE
> >> > oError:thread       :          1
> >> > oError:tries        :          0
> >> >
> >> > This has been quite frequent for many weeks. And also
XbpFont:create().
> >> >
> >> >
> >> >
> >> > oError:args         :
> >> >          -> VALTYPE: O CLASS: XbpFont
> >> > oError:canDefault   : N
> >> > oError:canRetry     : N
> >> > oError:canSubstitute: Y
> >> > oError:cargo        : NIL
> >> > oError:description  : Internal data structures corrupted
> >> > oError:filename     :
> >> > oError:genCode      :         41
> >> > oError:operation    : :create
> >> > oError:osCode       :          0
> >> > oError:severity     :          2
> >> > oError:subCode      :          5
> >> > oError:subSystem    : BASE
> >> > oError:thread       :          1
> >> > oError:tries        :          0
> >> >
> >> > In this case the error log ended here, no callstack, so it happened
> > during
> >> > error creation.
> >> >
> >> >
> >> >
> >> > oError:args         :
> >> >          -> VALTYPE: C VALUE: username
> >> > oError:canDefault   : N
> >> > oError:canRetry     : N
> >> > oError:canSubstitute: Y
> >> > oError:cargo        : NIL
> >> > oError:description  : Internal data structures corrupted
> >> > oError:filename     :
> >> > oError:genCode      :         41
> >> > oError:operation    : getEnv
> >> > oError:osCode       :          0
> >> > oError:severity     :          2
> >> > oError:subCode      :          5
> >> > oError:subSystem    : BASE
> >> > oError:thread       :          1
> >> > oError:tries        :          0
> >> >
> >> > This happened also during error log creation. Username would be part
of
> >> > it.
> >> > This is a quite new kind of error.
> >> >
> >> >
> >> >
> >> > oError:args         :
> >> >          -> VALTYPE: U VALUE: NIL
> >> >          -> VALTYPE: U VALUE: NIL
> >> >          -> VALTYPE: C VALUE: C:\VIL\TEGLA\DATA\qCtrl001
> >> >          -> VALTYPE: U VALUE: NIL
> >> >          -> VALTYPE: L VALUE: .F.
> >> > oError:canDefault   : Y
> >> > oError:canRetry     : Y
> >> > oError:canSubstitute: N
> >> > oError:cargo        : NIL
> >> > oError:description  : Internal data structures corrupted
> >> > oError:filename     :
> >> > oError:genCode      :         41
> >> > oError:operation    : DbUseArea
> >> > oError:osCode       :          0
> >> > oError:severity     :          2
> >> > oError:subCode      :          5
> >> > oError:subSystem    : BASE
> >> > oError:thread       :          1
> >> > oError:tries        :          1
> >> >
> >> > This is an exclusive open dbf.
> >> >
> >> >
> >> > And so on...  
> >> >
> >> >
> >> > These are quite unususal errors IMO, and the customer is quite
> > unsatisfied
> >> > because of it. They happens almost every day.
> >> > 1. What do you think the cause can be of this?
> >> > 2. What is responsible for an IDSC at all?
> >> > 3. When exactly does Xbase++ report such error?
> >> > 4. What does become corrupted?
> >> > 5. Can RAM error cause this?
> >> >
> >> > Thanks in advance for your help,
> >> > Otto
> >> >
> >> >
> >>
> >>
> >
> >
>
>