| Author |
 Topic  |
|
|
dcohn
New Member
98 Posts |
 Posted - 03 June 2007 : 14:48:14
|
I had someone create a test forum using 3.4.0.6. I had him apply the few mods I was using (active users lite, iespell (did not work for him switched to googiespell), stats and gatekeeper.
He had a seperate copy of the database for all testing.
Once everything seemed to work correctly I first compacted the database. To compact the database Snitz would give the result compact successful and then a permissions error to rename the compacted database over the original (forum was stopped). I then via FTP renamed the original database to .org and the compacted to the name of the live.
Everything was working as it should once restarted.
So I let him do the upgrade.
I had all kinds of issues which he resolved (missing quotes and things like that) except for this error.
Microsoft JET Database Engine error '80004005'
Could not use ''; file already in use.
/forums/inc_header.asp, line 111
which is OCCASSIONAL. Just now it occured when I attempted to log into the admin. Tried it again (after logging in again) and it worked fine).
Since it is intermittent I don't know where to look. Permissions were checkd, the database is on the same server (it is a Hosted account that has been working without any issues for over 18 months).
Obviously the changes he made including the updated to 3.4.0.6 are creating the problem.
Any ideas thoughts etc are greatly appreciated.
Doug |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 05 June 2007 : 13:21:36
|
This is basically a server related issue. I don't think this depends on whatever was done during the upgrade. If you have the option to upgrade to SQL Server or MySQL, I'd suggest that you do so.
|
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
dcohn
New Member
98 Posts |
Posted - 05 June 2007 : 13:51:52
|
I am very sorry about the double post. I thought because I was so wordy I wzas not getting a response. I will not do it again!
Is there anything you can recommend we look at do resolve this besides upgrading right now.
I did Compact the database using Snitz admin routine. It had to be manually renamed though because of a rights issue. I renamed it via FTP and evrything seemed OK. This was before the upgrade was done.
The database was 50 meg after upgrading |
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 05 June 2007 : 14:20:28
|
| I don't think much can be done. Microsoft states that this is a permissions issue, but permissions issues don't occur just once in a while, so I think this is server related. Unfortunately I don't see much you can do ... except upgrading... |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
dcohn
New Member
98 Posts |
Posted - 05 June 2007 : 18:36:36
|
| Yes I found the same info from Microsoft. It was brought on either by the update or the compacting of the database. I guess there could be some bug in the database that causes the issue but like you just said why only occasionally. Very weird. |
|
|
|
|
dcohn
New Member
98 Posts |
Posted - 05 June 2007 : 18:57:38
|
Is it possible that the ''; the two single quotes are somehow creating the problem????
As you see it specifies a line number. I know you already aid it is server related but a forum running for 18 months without a single burp, we upgrade and get this repeatedly just does not act like a coincidence. Agreed is there anything you can think of where the changes made can create this problem.
Could not use ''; file already in use. |
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 05 June 2007 : 20:16:32
|
| Honestly I don't think it has to do with the upgrade per se. I saw this happening in previous Snitz versions. Upgrading from 3.4.05 to 3.4.06, in terms of database, means changing one record and adding one or two records to FORUM_CONFIG_NEW. The existence of the line number just means that the code was trying to access the database when that happened, nothing else. You may try to take the forum down, download the database, use Access to compact and repair it and then upload it again. I don't think it will make a difference, but you can try. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
dcohn
New Member
98 Posts |
Posted - 06 June 2007 : 03:18:11
|
Access is so touchy. I don't know why they initially set it up in access but we started this forum on a whim. The host donated everything, never charged us a penny and we never imagined it would become such a busy forum so fast. Unluckily there are a lot of diabetic cat owners out there and even more vets that have no clue how to treat them.
If you have a cat do not feed it dry food no matter what you do or you too will be visiting this forum eventually.
http://www.yourdiabeticcat.com |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 06 June 2007 : 03:39:48
|
| Access was never meant to drive websites and there lies the whole question. Access support in Windows 2003 even worsened the scenario, that already was not very bright... |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
daveo
New Member
97 Posts |
Posted - 07 June 2007 : 20:08:38
|
| If you are using Access to drive a website I recommend using the ODBC driver, rather than connect via the Jet interface. I used access during my testing and then converted to SQL 2005. Express is free. SQL is so much better than Access. |
http://copdforum.portalone.us/ |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 07 June 2007 : 20:13:24
|
quote:
Originally posted by daveo
If you are using Access to drive a website I recommend using the ODBC driver, rather than connect via the Jet interface.
I most certainly don't. The experience I have here, since I started (about 6 years now) has always showed me that OLEDB drivers are faster and more robust 99,99% of the times.
I've always recommended OLEDB over ODBC. The improvement in performance, quite often, is impressive. Also, many times where you have ODBC related errors, OLEBD just works. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 08 June 2007 : 06:20:51
|
Though, daveo is right on the point that if you can get SQL Server 2005 Express its better than Access. 
Unfortunately its not always an option if you don't own the server. |
|
|
|
dcohn
New Member
98 Posts |
Posted - 09 June 2007 : 16:28:31
|
Surely not an option. This was a whim setup and the Host is an ISP who was my client as well (network support). So he gave us the site and setup a forum. Who imagined it would grow so large so fast (that so many people have sick cats from feeding them DRY FOOD).
No hosting company is going to use SQL Express. But if memory serves me correctly there is either a 5 user or 10 user (simul) limit on SQL Express. Could be an equally (more) frustrating problem on a growing forum. That is why it is free.
We are planning to migrate to MYSQL with the help of one of the wonderful people here on SNITZ. MYSQL just in case we ever have to move to a paying host. The site is all volunteer with no ads, no profits.
|
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 09 June 2007 : 21:23:35
|
That limit was with the MSDE. SQL 2005 Express has no limit on connections, but it only sees 1GB of RAM, 1 core, and has a 4GB limit on database sizes. (or was it table sizes...)
Lots of hosting companies use SQL Express because its free, uses the same core tech. as SQL 2005 (hence the name), and they usually don't want people using more than 4 GB without paying extra for it (and then they can move them to a full blown SQL Server, and charge them for it).
Both MySQL and the various flavors of SQL Server will be a big step up from Access. Personally, I tend to favor SQL Server as I've had less trouble... but that's just me. Others see it differently.
Good luck. |
|
|
|
asboyd
Starting Member
Australia
5 Posts |
Posted - 11 June 2007 : 18:34:10
|
I thought I might put in my tuppence worth here. I have been using Access to run my Forum for three years+ and have found a bit of an issue with the Access database. I have only used the inbuilt backup and compact option once. After it caused the Access error I then found it easier to backup to my local drive, make any changes (including archiving) then perform an Access Compact and Repair.
The resulting DB is then put back onto the server.
Since using this process I have never seen the error come back.
I know that SQL would be a better way of running my Forum but I ma at the mercy of an IT department that tries to thwart me using our own web server.
Regards,
AlexB |
|
|
| |
Topic |
|
Topic Locked
