Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Join this live chat April 6, 10AM EST - QlikView to Qlik Sense REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
varaprasad0816
Creator II
Creator II

SQL##f - SqlState: S0002, ErrorCode: 208, ErrorMsg: [Microsoft][ODBC SQL Server Driver][SQL Server]

Hi,

 

I am getting below mentioned error while reloading qlikview application with SQL connection string.

SQL##f - SqlState: S0002, ErrorCode: 208, ErrorMsg: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'Sabre GLBL Inc.Sabre GLBL Inc.User'.

I have loaded below mentioned SQL script in Qlikivew (have done some transformation) but getting an error as mentioned above.

 

ODBC CONNECT TO ASSLADB (XUserId is ZCEBdZRNBLYIWWFN, XPassword is ZCRDRQMKMCNOTZEMNTMATY);

SELECT

"Contact.Email",
"Case.CaseNumber",
"Case.ClosedDate",
"Account.Name",
"Contact.Name",
"Case.Product_Name__c",
"Case.Product_Line__c",
"Case.Account_Region__c",
"Case.Origin",
"Case.Customer_Impact__c",
"Case.Product_Suite__c",
"Case.Severity__c",
"Account.Airline_Code__c",
"Case.Subject",
"Case.Problem_Type__c",
"Case.Problem_Sub_Type__c",
"Case.System__c",
"Case.Type",
"Case.Owner_Employee_Number__c",
"Case.Status",
"Case.Sub_Status__c",
"Case.When_Found__c",
"Case.Responsible_Entity__c",
"Case.Resolved_by_Team__c",
"Account.Id",
"Contact.Id",
"Case.Account_Segment__c",
"Asset.Installation_Type__c",
"User_CaseOwner.LastName",
"User_CaseOwner.FirstName",
"RecordType_Case.Name",
"AccountTeamMember.TeamMemberRole",
"User_AD.LastName",
"User_AD.FirstName",
"AccountTeamMember.Id",
"AccountTeamMember.AccountId",
"Product2.Product_Tier__c",
"Case.Not_Visible_to_Customer__c",
"Case.Case_Business_Area__c",
"Contact.Do_not_CallEmail__c",
"Account.Focus_Account__c",
"Product2.Id",
"RecordType_Account.Name"

FROM (((((("Sabre GLBL Inc"."Sabre GLBL Inc.User" "User_CaseOwner"
INNER JOIN
"Sabre GLBL Inc"."Sabre GLBL Inc.Case" "Case"
ON "User_CaseOwner.Id"="Case.OwnerId")

INNER JOIN
("Sabre GLBL Inc"."Sabre GLBL Inc"."RecordType" "RecordType_Account"
INNER JOIN
"Sabre GLBL Inc"."Sabre GLBL Inc"."Account" "Account"
ON "RecordType_Account.Id"="Account.RecordTypeId")
ON "Case.AccountId"="Account.Id")

INNER JOIN "Sabre GLBL Inc"."Sabre GLBL Inc"."Contact" "Contact"
ON "Case.ContactId"="Contact.Id")

INNER JOIN "Sabre GLBL Inc"."Sabre GLBL Inc"."Asset" "Asset"
ON "Case.AssetId"="Asset.Id")

INNER JOIN "Sabre GLBL Inc"."Sabre GLBL Inc"."RecordType" "RecordType_Case"
ON "Case.RecordTypeId"="RecordType_Case.Id")

INNER JOIN ("Sabre GLBL Inc"."Sabre GLBL Inc"."User" "User_AD"
INNER JOIN "Sabre GLBL Inc"."Sabre GLBL Inc"."AccountTeamMember" "AccountTeamMember"
ON "User_AD.Id"="AccountTeamMember.UserId")
ON "Case.AccountId"="AccountTeamMember.AccountId")

INNER JOIN "Sabre GLBL Inc"."Sabre GLBL Inc"."Product2" "Product2"
ON "Asset.Product2Id"="Product2.Id"

WHERE "Case.Case_Business_Area__c"='Airline Solutions'
AND
"Case.Not_Visible_to_Customer__c"=0
AND
("AccountTeamMember.TeamMemberRole"='' OR "AccountTeamMember.TeamMemberRole"='Account Director')
AND
"RecordType_Case.Name"='AS Close'
AND
("Case.When_Found__c"='Maintenance' OR "Case.When_Found__c"='Production')
AND
("Case.Sub_Status__c"='1st Level'
OR "Case.Sub_Status__c"='1st Level (PS)'
OR "Case.Sub_Status__c"='2nd Level'
OR "Case.Sub_Status__c"='2nd Level (AS)'
OR "Case.Sub_Status__c"='2nd Level (PS)'
OR "Case.Sub_Status__c"='3rd Level (PS)'
OR "Case.Sub_Status__c"='Account Team'
OR "Case.Sub_Status__c"='Contract Admin'
OR "Case.Sub_Status__c"='Customer Response'
OR "Case.Sub_Status__c"='Delivery'
OR "Case.Sub_Status__c"='Development'
OR "Case.Sub_Status__c"='Development (AS)'
OR "Case.Sub_Status__c"='Further Action'
OR "Case.Sub_Status__c"='Further Prioritization'
OR "Case.Sub_Status__c"='N/A'
OR "Case.Sub_Status__c"='Next Release'
OR "Case.Sub_Status__c"='Open'
OR "Case.Sub_Status__c"='Operations'
OR "Case.Sub_Status__c"='Pending Acceptance'
OR "Case.Sub_Status__c"='Reopened'
OR "Case.Sub_Status__c"='Resolved'
OR "Case.Sub_Status__c"='SaaS Team'
OR "Case.Sub_Status__c"='SFDC Support'
OR "Case.Sub_Status__c"='Specialized Team'
OR "Case.Sub_Status__c"='Vendor'
OR "Case.Sub_Status__c"='Vendor (AS)'
OR "Case.Sub_Status__c"='Vendor (PS)'
OR "Case.Sub_Status__c"='Waiting for customer (PS)')

AND "Case.Status"='Closed'
AND NOT ("Account.Name"='EDS' OR "Account.Name"='Sabre Inc.')
AND "Case.ClosedDate">={ts '2019-10-02 00:00:00'}
AND NOT ("Contact.Email" LIKE '%@sabre.com' OR "Contact.Email" LIKE '%@Sabre.com' OR "Contact.Email" LIKE '%@sabre-holdings.com')
AND "Contact.Do_not_CallEmail__c"=0

ORDER BY "Case.CaseNumber";

 

Note : I am suspecting double quotations (" ") after "FROM" 

Request you to kindly go through the above mentioned script and guide me how to reload it successfully.

Labels (2)
1 Reply
Brett_Bleess
Support (Former)
Support (Former)

You would be better served posting this on the Microsoft SQL forums, as the error is in SQL, not QlikView, we are simply returning the error generated by the SQL ODBC connector, which in this case is the Microsoft SQL driver...  I did a quick search upon things and the only thing I ran across on our side was related to our generic ODBC connector and special characters in the object name.  From the Google search I ran, it could be multiple things, you will have to work through those to figure out which thing is the issue, but asking your SQL DBAs for a bit of help is likely the fastest option on this one, as they will likely know or be able to help you further troubleshoot things.  If you get further information that points to something we are doing wrong, let us know, but at the moment I believe this is on the Microsoft side, and they are the experts on their tech.  

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.