PDA

View Full Version : Can't initialize user Counting (timeout)



Tod Brannen
17-Jan-2006, 06:17 PM
Greetings,
I am using VDF 11.0 with SQL CK and I have not had any problems for the
last week or two connecting to the tables. Today I get the above error
trying to view the tables in dbExplorer, and I don't know if it is a VDF
error or SQL error or what to do about it. It says error # 12325 on Line #
46704. But if I click 'OK' it then shows me another error. The error is
"Table not open TableNumber=13, Source=API.Get_Attribute. Error #72 Line #
46721". What could cause this? I am using PC Anywhere to connect to the
user's machine and don't have the SQL server or tables in our office.

Thanks for looking,

Tod Brannen

Ben Weijers
18-Jan-2006, 04:35 AM
Tod,

Error 12325 is a CK error (it is even documented as a CK error).

Since you get this error, the table that dbExplorer is trying to open canot
be opened and that is why you get the second error. We never tested using PC
anywhere, I have no idea why this would happen. Can this user open tha table
from his machine if PC Anywhere is not used?

Regards,

Ben Weijers
Data Access Worldwide

Tod Brannen
18-Jan-2006, 11:12 AM
Ben,
I was able to find the 'doc' in the help. One line that just repeats the
error and does not tell how to fix it. Anyway, this has been working just
fine for weeks, why would it stop and give errors all of a sudden?
pcAnywhere is just a window on the desktop, it does nothing different, but
yes the error happens if it is not used. As I said, it has worked fine since
I installed it. ??? I am not using VDF to write to the SQL files, I only
read data and I don't use dbBuilder to modify the files in any way.

Thank you,

Tod Brannen

"Ben Weijers" <Ben.Weijers@dataaccess.nl> wrote in message
news:NGAQ5JBHGHA.5164@dacmail.dataaccess.com...
> Tod,
>
> Error 12325 is a CK error (it is even documented as a CK error).
>
> Since you get this error, the table that dbExplorer is trying to open
canot
> be opened and that is why you get the second error. We never tested using
PC
> anywhere, I have no idea why this would happen. Can this user open tha
table
> from his machine if PC Anywhere is not used?
>
> Regards,
>
> Ben Weijers
> Data Access Worldwide
>
>

Tod Brannen
18-Jan-2006, 11:57 AM
I read all the WASP and newsgroup articles I could find and there was not a
real solid explanation or cure. But, I did see one that said try rebooting
the computer. So I used the 'manual' method and it worked. The idea came
from a reply by Michael Salzlechner of Starzen, which stated " If for some
reason the daemon died or was called by CAD you will have to reboot.". So I
guess I had a dead daemon. Since it is a remote computer, I don't usually
reboot it for them, but in this case.... I just put this in here in case
someone else has the same problem.

Thanks,

Tod Brannen
"Tod Brannen" <tbrannen@ate.net> wrote in message
news:rd6Vyw7GGHA.1756@dacmail.dataaccess.com...
> Greetings,
> I am using VDF 11.0 with SQL CK and I have not had any problems for
the
> last week or two connecting to the tables. Today I get the above error
> trying to view the tables in dbExplorer, and I don't know if it is a VDF
> error or SQL error or what to do about it. It says error # 12325 on Line #
> 46704. But if I click 'OK' it then shows me another error. The error is
> "Table not open TableNumber=13, Source=API.Get_Attribute. Error #72 Line #
> 46721". What could cause this? I am using PC Anywhere to connect to the
> user's machine and don't have the SQL server or tables in our office.
>
> Thanks for looking,
>
> Tod Brannen
>
>

Knut Sparhell
25-Jan-2006, 08:12 PM
Tod Brannen wrote:
> I am using VDF 11.0 with SQL CK and I have not had any problems for the
> last week or two connecting to the tables. Today I get the above error
> trying to view the tables in dbExplorer, and I don't know if it is a VDF
> error or SQL error or what to do about it. It says error # 12325 on Line #
> 46704. But if I click 'OK' it then shows me another error. The error is
> "Table not open TableNumber=13, Source=API.Get_Attribute. Error #72 Line #
> 46721". What could cause this? I am using PC Anywhere to connect to the
> user's machine and don't have the SQL server or tables in our office.

It probably ha something to do with VDFDaemon.exe. Try a restart.

--
Knut Sparhell, Norway