You searched for the word(s): userid:79442

More Search Options

RSS Available

• Re: Restart on new Bin dlls

  Derek, I did write the scheduler, but I think your question is more around the topic of the resource installer. I am going to take a stab at an answer here, I'm not sure if it is what you are seeing or not, but at least it's possible that this is the case. There is a setting in machine.config that specifies how long to wait after an app restart command has been issued by the .NET framework. If this duration is exceeded, the work process is forced to recycle. By default, this is set to 5 seconds.

  Posted to Core Framework (Forum) by BigWebmaster on 10/16/2005

• Re: Pictures of DotNetNuke Breakfast at PDC05

  Hah, let's not simplify our process to arrive at a sound architecure. It wasn't just three sugar packets, it was one sugar packet and two different sugar alternatives. Dan

  Posted to DotNetNuke (Forum) by BigWebmaster on 9/15/2005

• Re: is there any solution for the Eventlog yet?

  Daniel, over on this thread you noted that you aren't seeing any of your custom logs. I'm not sure I fully understand the problem that you're having. Have you looked in your EventLog table to see how many records are in there? If so, are you stating that some of these records are not displayed in the Log Viewer? How many records are in the EventLog table, and how many are displayed on the Log Viewer? Which entries specifically aren't shown in the log viewer? Dan

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/26/2005

• Re: Howto Configure ScheduleHistoryItem Settings?

  Yes, sorry guys, this feature hasn't been added. I had the code written for this a while ago...it was part of some other stuff I was working on. And I cannot find it now. It seems like a simple addition, right? It's actually a bit tricky due to the way the scheduler works (schedule queue, multi-threading, etc.) Enhancements like this get bumped down the list because other priorities have taken precedence like web farm support, performance enhancements, blah blah. You know, you've heard it before

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: Problem with 3.1.1 and Log Viewer

  Follow this thread.

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: DNN 3.1.1 Eventlog not available

  I suspect the use of temp tables is the problem. In 3.1.1 I introduced paging in the log viewer. Well, paging was "kind of" there before, but it was a mediocre solution (created by yours truly). So, if this URL is correct, then we will need to add a collate clause wherever we use temp tables. I'm not familiar with this...I need to look at it further still. Dan

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: DNN 3.1.1 Eventlog not available

  Ok, it appears to be a problem with collation in SQL Server. The error is: Cannot resolve collation conflict for equal to operation. on this method: DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetLog(Int32 PageSize, Int32 PageIndex) I need to look into this further...not sure where the root of the problem is. Dan

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: DNN 3.1.1 Eventlog not available

  It sounds like it's a separate issue. That problem with {objectQualifier} should result in a failed install of the SQL scripts, meaning there would be info in the log file for 03.01.00 and 03.01.01 to indicate the SQL script threw erorrs. If you did not explicitly specify an objectQualifier in web.config, and you cannot see the eventLog, I am not sure what the problem is. First, verify that web.config is set to use the DBLoggingProvider as the default logging provider. If it is, then the only way

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: DNN 3.1.1 Eventlog not available

  If you have not explicitly specified an {objectQualifier} in web.config, then there is no impact. If you have specified an {objectQualifier} in web.config, then you would need to make the change above, and rerun the section of the script that failed in the >Host>SQL screen. But, I haven't tested rerunning that script. Technically SQL scripts are supposed to be re-runnable...but that's not always the case. It will take a couple days for me to find time to duplicate this problem and attempt to

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005

• Re: DNN 3.1.1 Eventlog not available

  Good catch, this is a bug. Did you log this in Gemini yet? Dan

  Posted to DotNetNuke (Forum) by BigWebmaster on 8/25/2005