If your log files are located on a network drive you need to enter your account name and password in the schedule options. When the scheduler runs as a system service it works under local service account and cannot access network without this authorization information. You also need to use full network (UNC) paths, mapped drives cannot work without manual mapping in this case.
It seems that there is some problems with permissions or security software in your system. There shouldn't be problems with accessing shared folders from the scheduler if UNC path is used, user account is specified and permissions for the folder are correct.
So I recommend to use the FTP server to access the logs. First of all you need to setup an FTP server. If you use IIS, you can use the built-in IIS FTP server. You can find detailed information on how to set up IIS in FTP here : http://learn.iis.net/page.aspx/263/in... and Creating a New FTP Site in IIS 7.
Alternatively you can use another FTP server, e.g. FileZilla FTP Server. FileZilla Server is free and easy to use.
In any case you need to configure FTP server to publish your log files.
After you have set the server, you need to configure WebLog Expert to download log files via FTP. To do it, you need to choose the FTP log location in Profile Properties > Log Files and enter FTP settings for your log files.
If you wish to analyze logs from load balanced servers and get report on them, you need to do the following:
1. Choose the "Multiple" log location mode in Profile Properties > Log Files.
2. Check the "Analyze log files from load balanced servers" option on the same page.
3. Add multiple log locations (one per each load balanced server). When you add a location, specify load balanced server name - it will be shown in report.
4. Check that the "Access Statistics > Servers" report is enabled in Options > Report > Contents.
After it you can analyze the profile and get the report for load balanced servers.
You need to specify a separate log source for each web server. The simplest way is if there are separate folders for the servers, in such case you can just create two sources like the following:
C:\Logs\Server1\*.log
C:\Logs\Server2\*.log
If all log files are places to the same folder you should check if it is possible to use wildcards to analyze logs for specific servers only. E.g. maybe it is possible to use wildcards like the following:
How to fix it?
I have tried the first method but it fails.
For the ftp method, what is the steps for the setting?
How to fix it?
So I recommend to use the FTP server to access the logs. First of all you need to setup an FTP server. If you use IIS, you can use the built-in IIS FTP server. You can find detailed information on how to set up IIS in FTP here : http://learn.iis.net/page.aspx/263/in... and Creating a New FTP Site in IIS 7.
Alternatively you can use another FTP server, e.g. FileZilla FTP Server. FileZilla Server is free and easy to use.
In any case you need to configure FTP server to publish your log files.
After you have set the server, you need to configure WebLog Expert to download log files via FTP. To do it, you need to choose the FTP log location in Profile Properties > Log Files and enter FTP settings for your log files.
How to fix it?
However, I am then facing another problem.
I found there are no load balanced server result.
How can I do it?
How to fix it?
1. Choose the "Multiple" log location mode in Profile Properties > Log Files.
2. Check the "Analyze log files from load balanced servers" option on the same page.
3. Add multiple log locations (one per each load balanced server). When you add a location, specify load balanced server name - it will be shown in report.
4. Check that the "Access Statistics > Servers" report is enabled in Options > Report > Contents.
After it you can analyze the profile and get the report for load balanced servers.
How to fix it?
Do the weblog expert still can interpret they are from two servers?
How to fix it?
C:\Logs\Server1\*.log
C:\Logs\Server2\*.log
If all log files are places to the same folder you should check if it is possible to use wildcards to analyze logs for specific servers only. E.g. maybe it is possible to use wildcards like the following:
C:\Logs\s1*.log
C:\Logs\s2*.log
What they refering to?
What they refering to?
What they refering to?
I use network drive for this.