Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Options
Server License Expired even though License is not expired
Mkublbock
Member Posts: 4
Hey there!
On of our systems we have multiple NAV Versions installed. When trying to open the DEV Env. for 2013 we get a warning saying "Your program license has expired". The unusual thing is that the Dev. Env. doesn't open at all, just the warning and then it's gone. We uploaded the license manually via the AdminTool Powershell but it still doesn't work.
When downloading and installing a fresh 2013 the same error occurrs. Anyone facing the same problem? We think that the license cannot be the problem, but we think it's likely that some recent Windows Update may cause this error.
On of our systems we have multiple NAV Versions installed. When trying to open the DEV Env. for 2013 we get a warning saying "Your program license has expired". The unusual thing is that the Dev. Env. doesn't open at all, just the warning and then it's gone. We uploaded the license manually via the AdminTool Powershell but it still doesn't work.
When downloading and installing a fresh 2013 the same error occurrs. Anyone facing the same problem? We think that the license cannot be the problem, but we think it's likely that some recent Windows Update may cause this error.
0
Answers