Actually, I think there's only one reliable way to refresh a document on a QlikView Server: let the Distribution Service reload & distribute it. All other "solutions" require one or more of the following: hacking, Windows account & permission twisting, fighting a reluctant QV Desktop, massaging Windows Task Scheduler to do what it is not made to do (for example chaining reload jobs), etc.
However, that doesn't mean you don't have any flexibility in how you start a reload. There are many QlikView architecture-compatible techniques like task chaining, triggering using external events (EDX), supporting tasks, manual triggers by QlikView Administrators or - and this is better for maintaining law & order on your server - Document administrators, and more.
YMMV
