Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV Web Client Turns Blank
superpuz
Member Posts: 53
The web client works before. But after what I did bellow, I get a blank page every time I access NAV using web client. These are what I did:
1. Create and import the .cer dan .crl file for chain trust certificate.
2. Create several windows user for trial working with "UserName" Credential Type
3. Update the service property to work with the certificate (ClientServicesCertificateThumbprint and NavUserPassword)
4. Update the windows client's ClientUserSettings.config to work with "UserName" Credential Type (ClientServicesCredentialType and DnsIdentity)
5. Update the web.config so that the webclient also works with the credential type (ClientServicesCredentialType and DnsIdentity)
6. Both windows and web client works properly.
7. For some reason that I don't know for sure, while I'm in windows client, and create a NavUserPassword user, there is a warning that I did not complete the required data for the user in the current credential type. I ignore it under the assumption that the windows client detect that the client open with UserName Credential type, but the windows user is empty in the user card.
8. Update the windows client's ClientUserSettings.config to work with "NavUserPassword" Credential Type (ClientServicesCredentialType)
9. I cannot log in to the windows client using the new NavUserPassword user I create in step 7.
10. than I tried to delete all record in User and Access Control table in SQL Server (is there more proper way to do this? because I cannot delete the user through windows client by the error that the user must be disabled and after the status is disabled, still I cannot delete the user under the same error).
11. I then enter the nav windows client using "Windows" credential type, create a windows user and a NavUserPassword user.
12. Update the windows client's ClientUserSettings.config to work with "NavUserPassword" Credential Type (ClientServicesCredentialType)
13. It works. The windows client ask me to change the password as I requested when creating the user. Also all seems normal. until
14. Update the web.config so that the webclient also works with the "NavUserPassword" credential type (ClientServicesCredentialType)
15. I call the url to open the web client:
a. It request a credential that seems to be a credential for a windows user (not NavUserPassword user since it ask for domain\username instead of the NAV user name without domain name. is that normal?
b. And so I tried entering the Windows user I created earlier (step 11) in the log on window but all I get is a Blank screen.
c. This still happens after changing the credential to either UserName or Windows.
is there anyone have any suggestion?
1. Create and import the .cer dan .crl file for chain trust certificate.
2. Create several windows user for trial working with "UserName" Credential Type
3. Update the service property to work with the certificate (ClientServicesCertificateThumbprint and NavUserPassword)
4. Update the windows client's ClientUserSettings.config to work with "UserName" Credential Type (ClientServicesCredentialType and DnsIdentity)
5. Update the web.config so that the webclient also works with the credential type (ClientServicesCredentialType and DnsIdentity)
6. Both windows and web client works properly.
7. For some reason that I don't know for sure, while I'm in windows client, and create a NavUserPassword user, there is a warning that I did not complete the required data for the user in the current credential type. I ignore it under the assumption that the windows client detect that the client open with UserName Credential type, but the windows user is empty in the user card.
8. Update the windows client's ClientUserSettings.config to work with "NavUserPassword" Credential Type (ClientServicesCredentialType)
9. I cannot log in to the windows client using the new NavUserPassword user I create in step 7.
10. than I tried to delete all record in User and Access Control table in SQL Server (is there more proper way to do this? because I cannot delete the user through windows client by the error that the user must be disabled and after the status is disabled, still I cannot delete the user under the same error).
11. I then enter the nav windows client using "Windows" credential type, create a windows user and a NavUserPassword user.
12. Update the windows client's ClientUserSettings.config to work with "NavUserPassword" Credential Type (ClientServicesCredentialType)
13. It works. The windows client ask me to change the password as I requested when creating the user. Also all seems normal. until
14. Update the web.config so that the webclient also works with the "NavUserPassword" credential type (ClientServicesCredentialType)
15. I call the url to open the web client:
a. It request a credential that seems to be a credential for a windows user (not NavUserPassword user since it ask for domain\username instead of the NAV user name without domain name. is that normal?
b. And so I tried entering the Windows user I created earlier (step 11) in the log on window but all I get is a Blank screen.
c. This still happens after changing the credential to either UserName or Windows.
is there anyone have any suggestion?
Regards and Thanks,
Superpuz
Superpuz
0