Can you reload it using QlikView Desktop client instead of reloading from server?
So that when the reload fails, it may throw some errors which will be very useful to solve this issue.
Also I would recommend to enable the generate log file option in the Document Properties of the qvw file.
It will be easy to identify what and where is the exact failing occurs.
Yeah, so we can run the reload manually, and it works fine. However, when we run it using the Management consile, or on a schedule, it fails. Here is the log entry why:
4/16/2012 10:24:40 AM: Error: Cannot open file 'F:\fmkr_excel\DSR.xlsx' The system cannot find the path specified.
F is a mapped drive. I can manually browse to the drive when I log in, and I can open the file, but because Excel is not installed on any of the machines, it opens in NotePad and looks like gobble-dee-gook. I did copy the data locally and opened it with Excel and the data and layout of data looked 100% correct. The odd part is that the QV Service account is a Domain account, and We use it to log in AND run the server. So one would think that if I log into the server and can do everything manually, when the services run the reload, they should all work as well. That is the odd part, this only fails when QVS tries to reload the file. By the way, the File we are refreshing is just a QVD generator.
I also checked the Services, they are all set to log in with the QlikView account correctly, they are all running in the Windows snap-in, and they are all running without issue account to the QMC.
Thanks all for the help. It turns out that we needed to use the fully Qualified Name. Here was the weird part. The account we use to log into the server is the same account that runs QVS. One would think that if you can run it manually, using QVS would work as well, becuase, after all, it is the same account. Apparently not, which does not completely suprise me. It was also very helpful to turn on the log file option in the document. The log files are not always as explicit, and the option to create a log file is often turned off by default and then forgotten.
Again, thanks for all the help.