Datapage Error "unable to write to db"

[Mike N.]

I'm testing ver4.0 and sending stats to datapage

I am getting an error when updating the database....."unable to write to database" When it is showing a file path in the update window, 2 different databases flash by (one old and one new) just before the error occurs.

The database is brand new and the path is correct in the comand line

Is this a 4.0 issue or a Datapage xstats11.tmp issue (writing from home forgot to check file size)?

The same database and the same program running in 3.5mr2 work just fine

any suggestions?

[Schrocknroll]

Did you delete the xstats11.tmp file then retry it?

[\v/inston]

sticky!

[Mike N.]

Did you delete the xstats11.tmp file then retry it?

I wrote the thread at home and didn't try it yet

[Matthew D. Hoedeman]

The xstats11.tmp file/update error is such a common one that I have a batchfile short-cut on the quick start bar that removes the xstats11.tmp file (from ALL the installs of Pcdmis) and replaces it with a 'good' empty file (one time the absence of the file casued a problem, so I replace it instead) and I will click on this shortcut before every run I start. No hoo-hoo, no problems, no lost data.

[Schrocknroll]

Matt,

I noticed you got to 200 posts. What, no "super duper extra special member" status yet?

[Matthew D. Hoedeman]

I do not need any accolade from this board for my 'super-duper-extra-special-member', just the adulation of the masses.

[mtalla]

reply

Or a madulation of the @$$e$

[Mike N.]

back on topic....Update to trouble using 4.0 and DP

The size of the xstats11.tmp WAS larger than Zero (when opened with wordpad it contained the results of all the last runs)....so I deleted it and crossed fingers and executed the program ......upon completion the program reported the same error as before...."unable to write to database"......when that error was canceled another popped up....."unable to lock database"......???

When this same program was saved back to 3.5 and executed there with same database and path all ran well without error......xstats11.tmp remained at file size of zero

Any suggestions from the DATAPAGE experts???

Ver 4.0 March 17th
Win XP

[SABarber]

Are you using the same computer, user login?
Is there a file size/date difference between any of these between pcdmis versions:
bds501f.dll
bwcc32.dll
cw3220.dll
dpupd32.dll
dpupdate.exe
owl501f.dll
RDM45W32.DLL

[Mike N.]

Are you using the same computer, user login?
Is there a file size/date difference between any of these between pcdmis versions:
bds501f.dll
bwcc32.dll
cw3220.dll
dpupd32.dll
dpupdate.exe
owl501f.dll
RDM45W32.DLL

I'm not at that job location, however I will check those files when I go there again (part time job)

What would be the reason for looking at these files for differences? v3.5mr2 -vs- 4.0release

[SABarber]

These files are for the data transfer between pcdmis & datapage. There might be a difference between dpupdate.exe & dpupd32.dll but that should be OK.

[SABarber]

For a test you could copy the XSTATS11.TMP file generated by V40, put it in the V35 directory and double click (run) DPUPDATE.EXE from the V35 directory. If it works the file generated by V40 is correct and the area of concern would be the data update process, if it still fails the XSTATS11.TMP file should be sent to B&S to look at.

[Mike N.]

awesome direction

very good I was looking for this exact type of direction as how to test this possible version issue. I will not be able to do so 'till next week thursday. If you have any other possible tests please post them as well. This will be printed and taken to the site. Thanks again

[J Temmen]

Try going into the datapage database file and delete the LOCKMGR.DBL and VISTA.TAF files.