View Error Log - Unable to save page view record

[AlexG]

After update to AC 7.0.2 I found this error in Error Log - Administration page - in View Error Log

3/14/2009 1:26:25 AM Error Unable to save page view record. Value cannot be null. Parameter name: String Value cannot be null. Parameter name: String
3/13/2009 1:23:30 AM Error Unable to save page view record. Value cannot be null. Parameter name: String Value cannot be null. Parameter name: String
3/12/2009 1:23:50 AM Error Unable to save page view record. Value cannot be null. Parameter name: String Value cannot be null. Parameter name: String

Help me to fix it?

[bhill]

we are getting it constantly now too, anyone know what this is?
thanks

[jmestep]

The code to save the page views changed in 7.0.2. You might still have the old code on some of the customized files if you didn't replace it.
For example, code on CategoryGridPage.ascx.cs changed from
CommerceBuilder.Services.AbleCommerceHttpModule.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);

to

CommerceBuilder.Reporting.PageView.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);

[napacabs]

The code to save the page views changed in 7.0.2. You might still have the old code on some of the customized files if you didn't replace it.
For example, code on CategoryGridPage.ascx.cs changed from
CommerceBuilder.Services.AbleCommerceHttpModule.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);

to

CommerceBuilder.Reporting.PageView.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);

Replaced this code, and still getting 4 to 5 an hour of "Unable to save page view record. Value cannot be null. Parameter name: String", is there anything else that would cause this error?

[BryanWarmoth]

Has there been any progress on finding out the cause of this error? We just recently upgraded to 7.0.3 and are experiencing the same thing. I've gone through and did a text search for "CommerceBuilder.Services.AbleCommerceHttpModule.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);" and replace all occurances in out website with "CommerceBuilder.Reporting.PageView.RegisterCatalogNode(this.CategoryId, CatalogNodeType.Category);". We are still seeing a lot of these errors coming through. Any ideas?

[WylieE]

Bump. Anyone?

Obviously, if we turn off page view tracking, the errors in the error log go away. We don't see any errors in the app.log though.

We'll get these errors in batches. Bryan has already gone through all of our code looking for the changes listed above. Are there additional changes we need to look for? If so, what are they?

[Logan Rhodehamel]

It has to be specific to a particular browser - something is not parsing correctly but the error message does not help me track it. I thought maybe it was a masked user agent, but that didn't seem to pan out.

[WylieE]

Logan, please let us know if there is any information we can provide or any tests we can do to help get this resolved.

[Logan Rhodehamel]

Logan, please let us know if there is any information we can provide or any tests we can do to help get this resolved.

If you have IIS logging turned on as well, and you can find the equivalent requests to your website that approximate the timestamp on the failed page view, it might help me figure out why this particular browser is having trouble. At least I think it's a browser.

I reviewed the code and could not spot any obvious reason for that error.

[AlexG]

This error in AC 7.0.3 only I have not this error in old vrsion!

[Logan Rhodehamel]

In 7.0.0, the error was silently caught - if there was a problem in saving the page view it was ignored without a warning.

And for later versions, I still highly suspect this is dependent on the browser. Perhaps a new browser that has come out that is causing some problem. I have already tried FF3.5 and IE8 using private mode. Neither of those were it. If someone can find a matching IIS log entry, it will go a long way toward proving or refuting this theory.

[Logan Rhodehamel]

Also I should mention, the impact of the error is minor.

1) The page view can't be logged so you are losing that tracking data
2) Your error message gets an entry

There isn't an impact to the user nor does it inhibit the operation of the site. The biggest problem is that the errors in the log clutter up and potentially distract from truly important messages.

[NLC]

Did anyone figure out how to prevent these? We're getting this too and it's filling up the log file rather quickly. Maybe it has to do with the Google Chrome browser?

[AlexG]

This is not the Google Chrome!
It's a bot (SE robot)!
Just delete it from your error log on admin side!
Developers of AC not fix it with additional patch.

[jmestep]

We have one site that will have thousands of entries like that. I haven't been able to track it down. I thought it might be because the site came from Able 5 and was passing special parameters in the querystring that weren't the same in Able 7 Able 5--> 7.0.3-->7.0.4 before they went live. I hadn't seen it in sites before, but I have seen it in another site since then.

[QmsInfoTech]

FYI

I finally got around to matching the errors with the IIS logs. Here is a typical entry:

2010-08-19 23:11:58 W3SVC3 67.222.137.249 GET /Category.aspx CategoryId=11 80 - 72.14.199.145 AdsBot-Google-Mobile+(+http://www.google.com/mobile/adsbot.html)+Mozilla+(iPhone;+U;+CPU+iPhone+OS+3+0+like+Mac+OS+X)+AppleWebKit+(KHTML,+like+Gecko)+Mobile+Safari 200 0 0 48713 331 377

Jerry

[QmsInfoTech]

A little more info:

The problem seems to be the Google Mobile bot because

2010-08-19 20:57:13 W3SVC3 67.222.137.249 GET /Category.aspx CategoryId=11 80 - 72.14.199.145 AdsBot-Google+(+http://www.google.com/adsbot.html) 200 0 0 45053 218 292

does NOT throw a logged error. Notice that it's hitting the exact same page.

Jerry

[jmestep]

Thanks for posting that. I hadn't been able to track it down and was getting ready to comparing IIS logs like you did.

[Endeavour]

Logan_AbleCommerce
So, is it safe to delete all the error messages that say "Unable to save page view record. Value cannot be null...etc."?

[Logan Rhodehamel]

Yes it is safe to delete them. We've repaired the problem in the 7.0.6 release.