Thanks for the reply Steve, been busy so I havnt had a lot of time to look at this but I was finally able to get back to it.
I ran process mon and it looks like the IIS logs and url scan logs are written by different processes?
Below is an extract from the process mon logs:
IIS logs:
1:24:22.6143231 PM System 4 IRP_MJ_CREATE \\iislogs.server.com.au\iislogs$\webserver02\W3SVC792429\ex081120.log SUCCESS Desired Access: Generic Write, Disposition: OpenIf, Options: Non-Directory File, Attributes: N, ShareMode: Read, AllocationSize: 0, OpenResult: Opened
URL Scan logs:
1:24:21.4265332 PM w3wp.exe 2540 IRP_MJ_CREATE \\iislogs.server.com.au\iislogs$\webserver02\URLScan\urlscan.112008.log LOGON FAILURE Desired Access: Generic Write, Read Attributes, Disposition: OpenIf, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
The iis logs are written by the system process and where as the url scan logs are written by the worker process (w3wp.exe). The worker process is running as Network Service.
The destination (\\iislogs.server.com.au\iislogs$) has everyone full permissions and anonymous users full permissions so I don’t understand why the worker process cant access the destination.
In the situation you have been able to get url scan to log over a unc was your worker process running as network service or a specified user?