Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Guys
I'm relatively new to Qlikview and I've installed Enterprise Server and Publisher and successfully loaded reports so they can be viewed through i.e. I am now having a problem with the auto reload schedule. I can set up the schedule fine and it will try to run the script but every time it fails, citing Error Count = 3. I have created a log from the qvd and it says there is a general script error.
07/02/2012 18:00:02: Execution started.
07/02/2012 18:00:02: QlikView Version:9.00.7808.9
07/02/2012 18:00:02: 0002 SET ThousandSep=','
07/02/2012 18:00:02: 0003 SET DecimalSep='.'
07/02/2012 18:00:02: 0004 SET MoneyThousandSep=','
07/02/2012 18:00:02: 0005 SET MoneyDecimalSep='.'
07/02/2012 18:00:02: 0006 SET MoneyFormat='£#,##0.00;-£#,##0.00'
07/02/2012 18:00:02: 0007 SET TimeFormat='hh:mm:ss'
07/02/2012 18:00:02: 0008 SET DateFormat='DD/MM/YYYY'
07/02/2012 18:00:02: 0009 SET TimestampFormat='DD/MM/YYYY hh:mm:ss[.fff]'
07/02/2012 18:00:02: 0010 SET MonthNames='Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec'
07/02/2012 18:00:02: 0011 SET DayNames='Mon;Tue;Wed;Thu;Fri;Sat;Sun'
07/02/2012 18:00:02: 0013 OLEDB CONNECT32 TO [Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CRM2011Live;Data Source=crm-sql;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=4996-CUSTSVC;Use Encryption for Data=False;Tag with column collation when possible=False]
07/02/2012 18:00:02: Error: Unknown statement
07/02/2012 18:00:02: General Script Error
07/02/2012 18:00:02: Execution Failed
07/02/2012 18:00:02: Execution finished.
It runs fine using Qlikview desktop, just won't work when I schedule a reload. Any ideas? It's driving me mad! I am using QV10 Desktop to develop and the Server build is 9.00.7808.9
Thanks in advance
Stu
Jerry
I think I've figured out what it was.
The problem was a connection string in my script which I had set to force 32 bit:
//OLEDB CONNECT32 TO [Provider=SQLOL.......
As the server is a 64 bit operating system I changed the connections to read:
OLEDB CONNECT TO [Provider=SQLOL........"
and it works! Seems that's the answer.
Much appreciated for replying and taking a look though - it prompted me to comment everything out and look line by line.
Stu
Hi
What is the unknown statement? Can you give us the scriptlines following the ODBC connection?
You are running Integrated Security, has the service user access to the database?
HI Jerry
Thanks for your reply.
I am using integrated security and access is fine - I tested using a blank QV report with just a connection and basic table in it and it ran. I've commented out all the script on the report I am having issues with (although there are several) and I am gradually adding the scripts back in chunk by chunk so I can hopefully identify the bit it doesn't like, I will post the script that is flagging up the error shortly.
Thanks
Stu
Jerry
I think I've figured out what it was.
The problem was a connection string in my script which I had set to force 32 bit:
//OLEDB CONNECT32 TO [Provider=SQLOL.......
As the server is a 64 bit operating system I changed the connections to read:
OLEDB CONNECT TO [Provider=SQLOL........"
and it works! Seems that's the answer.
Much appreciated for replying and taking a look though - it prompted me to comment everything out and look line by line.
Stu