Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Performance Management
Lawson Business Intelligence/Reporting/Crystal
Login to LBI Using Domain Account
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
252
Members:
0
Total:
252
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson Business Intelligence/Reporting/Crystal
Login to LBI Using Domain Account
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Layne
Basic Member
Posts: 24
4/11/2012 6:46 PM
We are using a domain account called LBICrystalReports to attempt to login a LBI Crystal Report. Going into MY REPORTS and editing the Data Settings \ Default User ID, we add the account using the following format for the Default User ID: GCSD\lbicrystalreports. GCSD is our domain. It will not work and the SQL log error shows that the report is attemping to login using SQL Server Authentificaiton even though the account is a domain account. The permission in SQL Server is sufficient for this account and it's setup to use Windows Authentification. Any ideas?
Matthew Nye
Veteran Member
Posts: 514
4/11/2012 7:19 PM
Layne,
I dont have the syntax off hand but youre going to have to create an override data source first and then add a value in "Additional Connection Attributes" to indicate that the connection is using a trusted source, i believe. something along the lines of Integrated Security=SSPI. Of coarse this is all assuming an OLE DB connection to SQL Server. Difference versions of SQL Server may require different attributes. this should get you started in the right direction.
if you dont mind, please post back your successful results.
hth
Matt
You are not authorized to post a reply.