PDA

View Full Version : Error starting application



Nicholas Herlick
27-Jan-2005, 06:01 PM
Our app is running at a site with Pervasive SQL V8. Some workstations run it
fine, but two other recently-added workstations cannot load the application.
Instead, two errors display: (a) Status 24012 referencing FILE.DDF, followed
by (b) Status 72 on first attempt to open a database. The latter is fatal
and the app does not load.

1. The mapped drive containing the Data folder is mapped correctly and
FILE.DDF is there.
2. The registry entries are correct, they agree with the mapped drive and
folders
3. The app's main folder is shared with Everyone set to Full Control.
4. All of the files are where they are supposed to be, and other
workstations run fine
5. The user whose PC is not working is an Administrator
6. Pervasive V8 client is installed and tests OK on his computer

The thing should load! Ouy. Any suggestions would be greatly appreciated.

Nick

--
- - - - - - - - - - - - - - - - -

Nicholas Herlick
President
Herlick Data Systems
1348 Magnolia Ave.
Redlands, CA 92373
Phone: 909-798-2898
Fax: 909-792-9651
Email: nick@memsys.com
Web: www.memsys.com

Anders Öhrt
28-Jan-2005, 05:08 AM
> Instead, two errors display: (a) Status 24012 referencing FILE.DDF

When you get an error like this, subtract 21000 and you have the pervasive
error:
"3012: Local engine is not accessible to the MicroKernel router". Check the
PSQL help about this, there are some hints as to what might be wrong.

// Anders

Nicholas Herlick
2-Feb-2005, 06:26 PM
I found the solution after eating up one of my five "Genie lamp rubs" at DAC
SupportNET and then because that didn't help, paid for a $99 single incident
service call at Pervasive. In hopes of helping others save time,
aggravation and money, here is what cured the problem...

The problem...

The end user set up new workstations, mapped to the correct application
folder, and correctly installed the Pervasive client. The app should have
worked, but instead, every attempt to load failed with "STATUS 24012
FILE.DDF". Followed by Status 72 and it crashed. Status 24012 is Pervasive
error 3012.

The solution...

The Pervasive techie figured out that the workstation "saw" the app server
at the wrong IP address, based on an incorrect entry in this file:

C:\WINNT\System32\Drivers\Etc\Hosts

where "Hosts" is a file tracking the IP address and server name of the host
server. The workstation that would NOT run the application had the wrong
server IP address in its "Hosts" file. Note: The same 24012 (3012) error
would occur if the "Hosts" file contained no reference to the server.

a line was corrected in the "Hosts" file to read...

192.168.2.7 Titan

where "Titan" is the VDF application server, associated with a corrected IP
address. Turns out that the workstation was used previously when server
Titan had a different network IP address. Apparently, whatever process (or
person) was supposed to update the "Hosts" file... anyway THAT didn't happen
until the Pervasive tech fixed it.

This seems like an unusual problem, but it is one that can, sometimes, come
up to bite the VDF developer, when dealing with legacy networks and third
party network admins. And yes... I am billing the client for the Pervasive
call. :)

Nick

"Nicholas Herlick" <nick@memsys.com> wrote in message
news:1mzMoQMBFHA.1912@dacmail.dataaccess.com...
> Our app is running at a site with Pervasive SQL V8. Some workstations run
it
> fine, but two other recently-added workstations cannot load the
application.
> Instead, two errors display: (a) Status 24012 referencing FILE.DDF,
followed
> by (b) Status 72 on first attempt to open a database. The latter is fatal
> and the app does not load.
>
> 1. The mapped drive containing the Data folder is mapped correctly and
> FILE.DDF is there.
> 2. The registry entries are correct, they agree with the mapped drive and
> folders
> 3. The app's main folder is shared with Everyone set to Full Control.
> 4. All of the files are where they are supposed to be, and other
> workstations run fine
> 5. The user whose PC is not working is an Administrator
> 6. Pervasive V8 client is installed and tests OK on his computer
>
> The thing should load! Ouy. Any suggestions would be greatly
appreciated.
>
> Nick
>
> --
> - - - - - - - - - - - - - - - - -
>
> Nicholas Herlick
> President
> Herlick Data Systems
> 1348 Magnolia Ave.
> Redlands, CA 92373
> Phone: 909-798-2898
> Fax: 909-792-9651
> Email: nick@memsys.com
> Web: www.memsys.com
>
>