DasBlog 1.8 Pingbacks not working

After my dasBlog 1.8 installation, I noticed that it doesn't seem to be able to handle pingbacks. Well, actually it accepts the pingback just fine from the remote server, generates the notification email correctly, but fails to save it to the .dayfeedback.xml file.

Instead, I see this in dasBlog event log:

Error:
System.IO.IOException: DasBlog.Util.FileUtils: Error accessing d:\websites\winterdomcom\Weblog\content\2006-02-21.dayfeedback.xml, perhaps it is in use by another process?
at newtelligence.DasBlog.Util.FileUtils.InternalAssertIfNull(FileStream file, String name) in C:\Dev\DasBlog CE\source\newtelligence.DasBlog.Util\FileUtils.cs:line 104
at newtelligence.DasBlog.Util.FileUtils.OpenForWrite(String fileName) in C:\Dev\DasBlog CE\source\newtelligence.DasBlog.Util\FileUtils.cs:line 35
at newtelligence.DasBlog.Runtime.DayExtra.Save(DataManager data) in C:\Dev\DasBlog CE\source\newtelligence.DasBlog.Runtime\DayExtra.cs:line 231
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.InternalAddTracking(Tracking tracking) in C:\Dev\DasBlog CE\source\newtelligence.DasBlog.Runtime\BlogDataService.cs:line 1425
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.TrackingHandler() in C:\Dev\DasBlog CE\source\newtelligence.DasBlog.Runtime\BlogDataService.cs:line 1448
while processing Unhandled Exception from TrackingHandler.



The specified .dayfeedback.xml file does not get created, actually, so I don't think locking is the problem here. Also, everything else (including comments and entries) get written correctly to the same directory, so I'm not sure it is a permissions issue.

Any ideas?

Comments (1)

Paul BallardMarch 5th, 2006 at 8:15 pm

You and I must have been having the exact same weekend. I spent most of mine putting up a ThinkJot/Dasblog blog site and I had the exact same problems. Here is how I solved them.
I solved the IOException issue by adding Network Service to the list of users with Read/Write permissions to the siteconfig, logs, and content directories. The key seems to be to make sure the ID of the identity that the application pool is using has rights, which in my case wasn’t ASPNET.
I also had a problem with the admin links not showing up. That turned out to be because the site was attempting to use the ASPNetRoleProvider, which DasBlog doesn’t use. You can turn that off in the ASP.NET Configuration tab in the properties window for your blog’s virtual directory.
Hope this helps,
Paul Ballard

Leave a comment

Your comment