Community Credit Forums

Sigh...

I'm back again, with an inability to run the Community-Credit add-on, but this time, the problem is on just one of my sites.  Unfortunately, it's the main site.  ( http://Home.UltraTech-llc.com/)

Once we confirmed that ASP.NET 2.0 was needed to run the addon, I upgraded my internal website and was able to confirm that the module worked, as I posted earlier.

Early this morning, I upgraded my main site to ASP.NET 2.0, but I had quite a few issues, which turned out to be related to a conflict, it seems, between the CCredit add-on and at least one other add-on, most likely the URL remapping one.  I didn't get my site back up until this afternoon, sometime, but in the meantime, I was able to upgrade my work installation to ASP.NET 2.0, and the CCredit module is running there as well.

Now, here's the fun part: I'm using the URL remapping module in all 3 locations, but I'm only experiencing failures on my public site.

Worse yet, except for the SQL connection strings in the Web.Config files used on my internal and public sites, all the other configuration files and DLLs are identical.  I push all the changes from one source tree to either the internal web server, or via FTP to my external provider.

I need some help understanding what the issue is here, because I am almost certain that it is something simple that I'm overlooking -- again.

I'll zip up my root config files so that they can be shipped to whomever needs to look at them.

When I was troubleshooting this evening, I made one single change in the file at a time between uploads so that I could be sure exactly when it broke.  Right now, on my public site, the code for CCredit is commented out, because if I enable it, the site breaks.  (And, unfortunately, I can't get the errors to display remotely via mode="Off", so I can't see what the actually conflict message is).

I may have gotten it working.  I'll verify in a day or so, with the details.

Thanks!

I am really sorry, Andrew, I totally abandoned you.  Between a recent CodeCamp and a hurricane coming through my town (false alarm in the end), I was offline for a little bit.  I see in the last email that you think you may have solved the problem.  Can you give me an update when you know one way or the other and I can jump in to troubleshoot it if there is anythingt that I can do.

Don't worry about it, David.   Life happens. 

In the end, I was way too optimistic.   There is something about the configuration of my public site that is different from the other two sites that is probably causing the issue.   Within the next two weeks, I'm going to setup a test site at the root of my domain and see if it still generates the problem.   I suspect that it won't.

All I really need to troubleshoot things where they are is to setup an HTTP handler for viewing my ASP errors remotely.  If I had that, I would know *exactly* what components were crashing, and I could resolve this much faster without setting up another site.

I'll try to get to that over the weekend, assuming my wife doesn't kill me first

This is the post I will be working from: http://www.aspnix.com/forums/permalink/10512/10517/ShowThread.aspx#10517