User login

MetaTraffic 2.0 Boxshot

Requires Update?

Posted by Ckudrna [November 14, 2003]

Hello friends,
I had the new version of metatraffic working GREAT on a hobby site, and i downloaded the DB file to clean out some invalid entries (visits from my IP before i set the config to not log my ip) and tried to upload it back, and after it copied, when I go to look at some reports, i get an error "Error Type:
Microsoft JET Database Engine (0x80004005)
Operation must use an updateable query.
/metatraffic/class.asp, line XXXX"

(this error is when i go to reffer reports. I get similar errors for language, keywords, screen size, etc.

I did not change any permissions on the server or anything, since I did everything remotely from AZ when my server is in Chicago.

I did not change anything in the config, class, or any other files required by metatraffic. Again, I could not have changed any permissions on the server, since I am 1500 miles away from the server........

All I did was download the database, delete a few records, and upload the file back to the server, and now it doesnt work.

Thank you very much,

CMK

Requires Update?

Good day,

When you say the new version, are you referring to v1.3?

Could you provide us with the "xxxx" number, so that we know where to look in the script, along with the SQL statement ?

For debugging, consider to add a Response.Write of the SQL statement prior to have it executed, this will help to pin-point the problem.

I recall seeing such an error, when I was doing modifications to the scripts, but I don't recall precisely what was the cause.

One of the circumstances I recall is when an INSERT was attempted and one of the field was set to "null", however the corresponding field's definition in the table did not allow insertion of nulls.

This is only one of the many circumstances I encountered while "playing" around with the scripts.

What can be done also is copy/paste the resulting query, then within Access open the QBE (Query by example) interface. Select SQL with the top left button. Paste the query in the window and run it. MsAccess/JET may report more descriptive message than OLE/ODBC.

Happy tracking...

Requires Update?

This is getting more complicated than it has to.

All I did was take out a few RECORDS from the database, and re-upload it. I did not change the DB schema, I did not touch any of the scripts.

Maybe I will just try reinstalling the whole thing and copy/pasting my old records (100,000's) into the new DB file and see if that works.

I dont get why it would work one minute and then when a few records are gone produce errors. Very strange

Requires Update?

Good day,

Indeed, this is a really strange situation.

Consider doing the 2 following checkpoints :

1) Ensure you're not exceeding your Disk Quota allowed at the creation of your account. With 100,000 records and using the original DB schema, I'm suspecting a fairly substantial disk space requirement to hold that file.

2) Verify with your web hosting service that the Update privilege did not inadvertly got removed from the directory where your DB resides.

You may consider create a very small DB with a couple of records, upload it with a test page to delete a record, in the same directory as your current MT database. If that test page fails, the odds are that the Write permissions got removed on you.

I extensively modified the scripts to accomodate needs and normalize the data, and beside some typo errors induced during the process, the 2 items above are mainly the ones that caused me griefs during the transition, along with MDAC and the Scripting engine. Also, if the web hosting service applied some "hotfixes", they may have impacted IIS, so testing with other applications/databases will confirm if in fact MT or its components are at fault.

Also, compare the settings you have locally and the ones on your web site. I understand that the DB is large, however if the settings are identical, try the logging process via you own local IIS/PWS, to ensure that the overall thing is working as expected.

Happy tracking!

Requires Update?

The "updateable query" error is the most common problem people have when installing MetaTraffic and is documented in the readme file included with MetaTraffic and on the support site! :) The solution is to ensure the IUSR_machine account has write access to the database file and the folder it is in. See the installation faq for more information including a link to Microsoft's knowledge base.

Regards,
~Chad

Requires Update?

Good day,

Chad, I agree with you that the requirements are mentioned in the documentation however since there were already 100K records in Ckudrna's database, I made the assumption that the setup was fine as is.

If the tracker is working one day and stops working on another day, then unless the tracker's files were moved to a different directory which doesn't have proper accesses, or the write-permission got removed by the IIS admin without advice, it becomes very difficult to determine the cause of such a situation.

Knowing that write-permissions may quite oftenly be the culprit, I would suggest a simple troubleshooting page that could be invoked to determine if in fact the host is meeting the requirements.

Requirements that could be evaluated are the Scripting engine versions, ensuring the db can be in fact accessed as per the actual settings, proper "track.js" specifications, write permission to the db, only to name these.

Assuming FSO is available on the hosting server, most of the settings could be verified/adjusted/set via a form, pretty much like the configuration for the Snitz forum you're running on the site, although it doesn't need to be as sophisticated, which would make the overall product environement even more easier to configure.

Also, the same page could be used to generate a text file with the installation specs, which in turn could either be copied/pasted or simply sent to the support staff. I've seen many situations that resulted in a faulty configuration, therefore having the key elements handy could simplify everyones life, save down time and obviously minimize/eliminate guesses which quite oftenly lead to wrong diagnostics.

Just my 2 cents.

Regards.