Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
BA Configurator fails to login
JanM
Member Posts: 15
Hi
We are trying to setup Business Analytics with NAV 5.0 with the Cronus DB on SQL Server 2005. After entering configurtor path db name and db-instance we start the configurator. The first steps initialize, check for sql server and analysis server are sucessfull. The next steps faild on position one Build Internal Representation with the error: Login error for the user su. This user has all rights on the sql server also we synchronized the logins from Navision. What else must be done to solve this security issue?
Thanks for any help.
Jan
We are trying to setup Business Analytics with NAV 5.0 with the Cronus DB on SQL Server 2005. After entering configurtor path db name and db-instance we start the configurator. The first steps initialize, check for sql server and analysis server are sucessfull. The next steps faild on position one Build Internal Representation with the error: Login error for the user su. This user has all rights on the sql server also we synchronized the logins from Navision. What else must be done to solve this security issue?
Thanks for any help.
Jan
0
Comments
http://www.mibuso.com/forum/viewtopic.php?t=16063
http://www.mibuso.com/forum/viewtopic.p ... sql+server
The main things are:
1. hardcode the server name in the StartConfigurator function in BA Database (table 700)
2. use the configurator for SQL 2005, even if the database is on SQL Server 2000; the latest configurator is substantially different, and seems to have fixed some bugs present in the old version.