Reloading Document Works in Designer But Fails in QV Server

[asmithids]

Hello,

I am able to reload a specific document in Designer, but the reload fails in QV Server.  I am getting the following error. The document does not have Section Access so I am not sure why section access is flagged in the error message (see bold and underlined text).

Has anyone experienced this error and resolved? 

Thank you in advance for any help with this issue. 

Error: The task "UserApps/Sales Performance - New Model.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=D:\QVSERVER\USERAPPS\Sales Performance - New Model.qvw.  ||    at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult) ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    --- End of inner exception stack trace --- ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    --- End of inner exception stack trace --- ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

[maksim_senin]

Hi,

Just as assumptions:

1. Maybe there user name and password are entered in reload task settings at Reload tab

2. Maybe your Section Access is in hidden script

Best regards,

Maxim

[#3]

Hello Smith,

With Which user you are loading data on Server? Is same as user you are using when loading from designer?

Check the .qvw Text document that will give you more details about error.

[awhitfield]

Hi Alec,

it's most likely a permission issue in that the QV Service users does not have the same access rights to either the data source or qv files involved in the reload as the user running the reload from QV Desktop. If not already done, the set the qvw to "generate a logfile", save and repeat the QMC based reload. The file created will contain more useful information.

HTH Andy