Hi All,

I have created a version of DNN 4.3.6 that will work on in this situation. Please note the following

Basically I have created a version that does not do the EventQueue code has been removed from the App Start and I have created a schedule that will execute this code.

Below are more details on what I have changed

Global.asax.vb

In the Application_Start start method added the following to the top of the method
Code:

DotNetNuke.Common.ApplicationIdentity = System.Security.Principal.WindowsIdentity.GetCurrent()

Commented out the following lines at the end of the method these are the lines that course the issue)
Code:

Dim oEventController As New EventQueue.EventQueueController
oEventController.ProcessMessages("Application_Start")

In the DotNetNuke.Library in the Globals.vb file

Added the following private member
Code:

Private _ApplicationIdentity As System.Security.Principal.WindowsIdentity

Added the following Property
Code:

Public Property ApplicationIdentity() As System.Security.Principal.WindowsIdentity
Get
Return _ApplicationIdentity
End Get
Set(ByVal value As System.Security.Principal.WindowsIdentity)
_ApplicationIdentity = value
End Set
End Property

In the HttpModule.UrlRewrite module, within the UrlRewriteModule.vb file

Added the following to the OnBeginRequest method
Code:

' Check that the services are running under the current user
If DotNetNuke.Common.ApplicationIdentity.Name <> System.Security.Principal.WindowsIdentity.GetCurrent().Name Then
DotNetNuke.Common.ApplicationIdentity = System.Security.Principal.WindowsIdentity.GetCurrent()
End If



Within the Provider.DNNScheduler module, within the ProcessGroup.vb file

In the Run method change the following
Code:

Try
                    Process.ScheduleHistoryItem.Succeeded = False
                    Process.DoWork()
                Catch exc As Exception
                    'in case the scheduler client
                    'didn't have proper exception handling
                    'make sure we fire the Errored event
                    If Not Process Is Nothing Then
                        Process.ScheduleHistoryItem.Succeeded = False
                        Process.Errored(exc)
                    End If
                End Try

To this
Code:

Dim changedIdentity As Boolean = False
Dim wi As System.Security.Principal.WindowsImpersonationContext
Try
Process.ScheduleHistoryItem.Succeeded = False
If System.Security.Principal.WindowsIdentity.GetCurrent.Name <> Common.ApplicationIdentity.Name Then
wi = Common.ApplicationIdentity.Impersonate()
changedIdentity = True
End If
Process.DoWork()
If changedIdentity Then
wi.Undo()
End If
Catch exc As Exception
'in case the scheduler client
'didn't have proper exception handling
'make sure we fire the Errored event
If Not Process Is Nothing Then
Process.ScheduleHistoryItem.Succeeded = False
Process.Errored(exc)
End If
If changedIdentity Then
wi.Undo()
End If
End Try


Now for the standard Warrenty

There is no Warrenty with any of this code, I have ran and tested this on my hosting company. If you use it, it is at your risk please always test first. This alteration will make sure that the schedule provider runs the code as the correct user. Also by cometing out the code in the Application_Start it does not try to do the EventQueue stuff as the wrong user. However, this also means that the event queue code never runs at app start. I created a schedule to do this everyday.

I tried using the Init however, at this point the it is still running under the AppPool user.

Yes I'm enforcing impercination, since I did not want to alter too much code. It should be possible to have an additinal setting within the schedule provider. This setting, could indicate what account you want it to run under. Maybe, the option of AppPool account, or Web Account.

[QUOTE]John Mitchell wrote

Taking the code from the App_start for the EventQueue will keep the messages from being processed at the time of the Event.  I don't see the code to actually do the processing,

[/Quote]

True, it does not run the EventQueue code. I have done this by adding a new schedule that I wrote.

[QUOTE]John Mitchell wrote

but if you are running those same statements only daily then it changes it to be a batch process with a JobQueue. 

[/Quote]

The reason I set it to run on a daily basis is that when I set it to run at AppStart. I knew that it would fail so I set it to retry after 5 minutes (thinking at this point the Website should be running under the correct account. However, when I was looking at the schedule history and when it was next ment to run, it keep increasing the time that is was suppose to run. Therefore, it never reattempted to execute the schedule

As mentioned, I wrote a schedule to execute the EventQueue code that should be ran in the AppStart. But as I said before, having it retry after 5 minutes was not working (i.e. it never ran). I'm not saying that this is the best solution. However, it works for the time being. Until the core team manage to figure out a better solution.

Ken