Re: Access and Corrupt DB
On Mon, Apr 22, 2002 at 02:02:05PM -0400, William Jojo wrote: It would be from [homes] h:\db#.mdb where # is the attempt number that we did at that time...are you checking the 222 and 223a versions of the logs? Yes, I'm looking at both these logs. The only difference I can see is that in the 2.2.2 log the open for My Documents\db7.mdb succeeds because the file is there, and in the 2.2.3a log it fails as the file is not. Can you completely wipe the profile for this user and just try it (Access) against a Samba 2.2.4pre server that isn't serving profiles as well on a mapped drive that is only serving the shared access db files. That should simplify this log considerably and enable me to find out what the problem is. Can you give me a telephone number and timezone so I can call you about this - it's my last showstopper before 2.2.4 Thanks, Jeremy.
Re: Access and Corrupt DB
On Mon, Apr 22, 2002 at 11:47:42AM -0400, William Jojo wrote: I'm posting this again. Jeremy, this seems very bad. We are running AIX 4.3.3 with 2.2.4-pre AND 5.1.0 with 2.2.4-pre. The problem is when you reopen a table you just created, MS-Access hurls and indicates the Visual Basic application database is corrupt. * This happens when you have the database on a Samba share. * This does NOT happen when saved to the C: drive. * MS-Office (2000 and XP) is served from a Samba share. * Office-2000 *and* Office XP do it when the database is on a Samba share. * The same error occurs on 2.2.3 and 2.2.3a. * Samba 2.2.2 and earlier does *NOT* have the problem. * There is a log at http://www.hvcc.edu:/~jojowil If there is anything more I can provide, please let me know...I'd like to see this fixed for 2.2.4 release. What I need is a debug level 10 log of the same operations performed to a 2.2.2 server where it works, and a debug level 10 log of *exactly* the same operation to a current (ie. CVS update from today) of SAMBA_2_2 server where it fails. There was a day around friday or so where the CVS tree had a bug w.r.t. error code returns that I fixed so a current checkout is essential. Can you get these to me asap ? Thanks, Jeremy.
Re: Access and Corrupt DB
Already on the web sitecurrent check out 8:15 EDT this morning...still there :( Bill On Mon, 22 Apr 2002, Jeremy Allison wrote: On Mon, Apr 22, 2002 at 11:47:42AM -0400, William Jojo wrote: I'm posting this again. Jeremy, this seems very bad. We are running AIX 4.3.3 with 2.2.4-pre AND 5.1.0 with 2.2.4-pre. The problem is when you reopen a table you just created, MS-Access hurls and indicates the Visual Basic application database is corrupt. * This happens when you have the database on a Samba share. * This does NOT happen when saved to the C: drive. * MS-Office (2000 and XP) is served from a Samba share. * Office-2000 *and* Office XP do it when the database is on a Samba share. * The same error occurs on 2.2.3 and 2.2.3a. * Samba 2.2.2 and earlier does *NOT* have the problem. * There is a log at http://www.hvcc.edu:/~jojowil If there is anything more I can provide, please let me know...I'd like to see this fixed for 2.2.4 release. What I need is a debug level 10 log of the same operations performed to a 2.2.2 server where it works, and a debug level 10 log of *exactly* the same operation to a current (ie. CVS update from today) of SAMBA_2_2 server where it fails. There was a day around friday or so where the CVS tree had a bug w.r.t. error code returns that I fixed so a current checkout is essential. Can you get these to me asap ? Thanks, Jeremy.
