60 fields found: Day, Release Time, Call Duration, Drop Reason, Details, RRC Release Cause, RANAP Release Group Name, RANAP Release Cause, RAB, Lat, Long, IMSI, IMEI, SV, Vendor, Model, Delta Time from Last MR, RAN ID Parameter, Drop Causing Cell, CPM, Access RNC Name, Access Sector, Access Distance, Access Ec/Io, RNC Module ID, Procedure, Evaluation, Cause, Extended Cause, Establishment Cause, Carrier, Active Leg 1 Sector, Active Leg 2 Sector, Active Leg 3 Sector, Active Leg 4 Sector, Active Leg 1 Ec/Io, Active Leg 2 Ec/Io, Active Leg 3 Ec/Io, Active Leg 4 Ec/Io, Active Leg 1 RSCP, Active Leg 2 RSCP, Active Leg 3 RSCP, Active Leg 4 RSCP, Active Leg 1 UL Interference, Active Leg 2 UL Interference, Active Leg 3 UL Interference, Active Leg 4 UL Interference, Active Leg 1 DL TCH Power, Active Leg 2 DL TCH Power, Active Leg 3 DL TCH Power, Active Leg 4 DL TCH Power, Candidate Leg 1 Sector, Candidate Leg 2 Sector, Candidate Leg 3 Sector, Candidate Leg 1 Ec/Io, Candidate Leg 2 Ec/Io, Candidate Leg 3 Ec/Io, Candidate Leg 1 RSCP, Candidate Leg 2 RSCP, Candidate Leg 3 RSCP, 2,064,408 lines fetched 11/9/2016 6:16:08 PM: 0015
11/9/2016 6:16:08 PM: 0023 Next File 11/9/2016 6:16:08 PM: 0009
IF NoOfRows('DropReport')>0 Then 11/9/2016 6:16:08 PM: 0010
Re: qlikview server machine crashes Error: Error: File extdata.cpp, Line 2903
For troubleshooting it is recommended to run the failing query in a third party SQL query tool, with the following considerations.
Use the same ODBC or OLEDB connection
Use the same underlying database driver
Access the same database server
Use the same user credentials, username and password. NOTE: Use the QlikView service user if issue is related to QlikView Server
The third party tool should return an unexpected result. In this context pay extra attention to that the field names are exactly as expected and in readable language without garbage characters.
Common resolution is to correct SQL query so that a valid and expected result is returned by database.
The error message comes from QlikView engine and is related to the database result not having valid fields. Typically this is due to the usage of LOAD * , which means that QlikView will parse the resuls in order to find the returned field names. For some reason the data base has not returned a valid result, most likely due to database driver issues or an invalid SQL query. If this does not resolve your issue, please log a case with Qlik Support. However if it does, please mark this as the correct answer.