Scheduler won't run on Server

Dr. Who

12 years ago
updated 11 years ago

I am trying to migrate WebLog Expert off an Windows XP machine in my office to a Server 2008 box in the server room. I've used the help information and have the program running under IIS and can manually analyze profiles.

However, I can't get the scheduler to work. It reports "There are no log files to analyze". I have read the information:

5.3 I get error "No log files to analyze" when I run analysis from the scheduler, how can I fix it?
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.

All my logfiles are on the respective webservers and not on the server where WebLog Expert is running. I setup the mappings just as they exist on my local PC. We setup another user account (instead of mine) and put that into the Scheduler settings. I can take the UNC path logged in as myself or this other account and paste it into the File Explorer and it will take me to that server where the logfiles exist.

Any ideas?

Replies 7

Oldest first
Newest first Oldest first

12 years ago

I tried another item I found without success that said:

You should try to specify a different local account (e.g. admininstrator account) in the schedule settings. If it doesn't work, you can try to select "Local system account" in the schedule options and then enter account settings in the properties of the "WebLog Expert Schedule Service" ("Log On" tab) in the Windows service settings.

Reply Link

Michael

The main difference with using the scheduler is that when it runs the program under a specific account, mapped drives aren't mapped. However, if full UNC paths are used and a specified account has rights to access it, it should work in most cases.

Maybe there is some security settings that don't allow the program to access the network shares when running from the system service. I recommend you to check the rights for the shares and also check firewall settings (if you use it).

You can also get more detailed information on the issue by adding an additional command in the task pre-processing. E.g. you can add the command like this:

dir //share/dir > C:\Temp\UNCTest.txt
After you run the task, you'll be able to check the UNCTest.txt file, maybe it will contain additional error information.

You can also try to use the Windows Task Scheduler. You can use a command line like the following:

"C:\Program Files (x86)\WebLog Expert\WLExpert.exe" -FromScheduler "Sample"
You can find information on the command line parameters in the program help. The -FromScheduler parameter isn't documented, it sets the program to write information to the schedule log.

When you add the task in the Task Scheduler, you need to choose the "Run whether user is logged or not" option. In most cases the Task Scheduler with this option should work the same way as the built-in scheduler, but it has more settings so maybe you'll be able to find a setting to avoid the issue.

Not getting the other account to work but I do get it to work under the Windows Task Scheduler for my account. I'll keep working at it to see what is up.

But, had a question if teh Windows Task Scheduler is the solution. I have logs for some websites on the server where WebLog Expert is running and more current ones on the webserver. I move them to local to free up room on the webserver. I know about doing mutiple log files but with the Windows Task Scheduler won't it analyze the local logs with the WebLog Expert Scheduler then fail on the remote logs. Then when the Windows Task Scheduler fires up it will redo the local logfiles and then do the remote logfiles. Will I end up doing something to the WebLog Expert Scheduler so it doesn't run the profile with the local files? I realize this isn't a big deal but it seems a waste to redo the local logs twice.

I'm not sure I understood your question. You have mentioned "WebLog Expert Scheduler" - do you mean the built-in scheduler or the program running with the -FromScheduler parameter?

If you use the Windows Task Scheduler, you shouldn't use the built-in scheduler. The Windows Task Scheduler will work the same way as the built-in scheduler as in fact all the analysis will be performed by the program itself (WLExpert.exe), and the schedulers just start it at the specified time under the specified account. The only difference is that the built-in scheduler doesn't run more than one task at the same time, and you should set the Windows Task Scheduler so it doesn't have overlapping WebLog Expert tasks. The best way to do it is to use one task running daily. You can use wildcards or the batch command line mode to analyze multiple profiles in one task.

If I understand correctly, the main problem is that you have some logs for specific servers on that servers, and some (archived) logs on the server where WebLog Expert is running, and you move (archive) some logs from time to time. If it so, you can set WebLog Expert to analyze both archived and non-archived logs, but when you move logs, the program will need to reanalyze all the logs. The best way to handle the issue is to move logs to the server where WebLog Expert is running regularly (e.g. daily) and then analyze only these logs.

Sorry. Too much going on today and the brain isn't working real clear.

Yes, I was talking about the built-in scheduler. If I get the Windows Task Scheduler to work under the other user account, then I would stop the built-in scheduler so both aren't running. That makes sense since the program I am running in the Windows Task Scheduler is WLEpert.exe.

So, I would fire off one task to run all the profiles. If that is the case then maybe I'll just run it under my username since that does work. I was afraid of using my username and then having to change my password on all the tasks when I updated my password.

You understood what I was talking about for the mutiple locations for logfiles. I understand the issues with moving them periodically and the program having to redo those logfiles that were moved. But, I don't want to get into the habit of moving logfiles each day. I did that at a previous job and it takes too much time to keep donig that item. I would prefer to only do it once a month or more. Anyway, since you said not to use the built-in scheduler if I use the Windows Task Scheduler, this won't be an issue.

11 years ago

I seem to be getting it under my username with the Windows Task Scheduler and the command "C:\Program Files (x86)\WebLog Expert\WLExpert.exe" -FromScheduler "Sample". I suspect there is an issue with the other username where it can't run a batch process or at least that is the message I am getting.

What I am curious about is the "-FromScheduler "Sample"" portion of the command. Is the name it is picking up from the profiles in WebLog Expert or the names I created in the WebLog Expert Scheduler? I can't seem to tell even if I rename some of the profiles or scheduled tasks. I am looking to figure out which it is so I can run the tasks correctly.

The "Sample" name is the name of the profile specified in the task properties ("Action" tab) in the schedule settings. You can specify any profile name here, or you can use a wildcard like * (to process all the profiles), "Site*" (to process all the profiles with name starting with "Site"), etc.