Developers Toolkit Import Error
 
            
                
                    Nitesh                
                
                    Member Posts: 43                
            
                        
            
                    Iam using Developers Toolkit to check my code changes. But when i try to import any of object i get the following error,
'The language of the file to import does not match the language of the .stx file. Import stopped!'
any solution for this error?
                'The language of the file to import does not match the language of the .stx file. Import stopped!'
any solution for this error?
0                
            Comments
- 
            When you import the file to you select the localized .stx?0
- 
            I select .stx file which is located in folder of toolkit itself.0
- 
            Try with the localized .stx that is found in your client folder.0
- 
            That doesnt work.0
- 
            When you created the Toolkit database was the client switched in English or your local language?0
- 
            The language was english.0
- 
            Ok. Open the Nav client in your local (Indian?) language. Create the database, import the objects and the try again.0
- 
            That does not work.0
- 
            I used to get this error plenty of times. But then I got the hang of it. For me the following works. I create the database with the client in Local language. I export the text files also with the same settings. Then in Toolkit I use the default language from my Nav installation folder...
 I don't remember any mention of this being in the manuals though (I haven't checked the latest version's manuals to tell you the truth). Has anyone else found exactly when the error occurs?0
- 
            Check your cside client folder in MBS.
 The .stx file and .flf file must be belonging to different countries.
 Just check it.
 Both of them must belong to same version and country...0
- 
            The .flf and .stx file that you import while installing Dev. toolkit must belong to same country.
 Just take care about this fact.0
- 
            I am having the same problem.. I have changed all the necessary .stx files on my machine but it still complains of this error. Both the stx and flf are from the same country...0
- 
            I had the same problem.
 In my case it was not the stx file which caused the trouble but the flf.
 Make sure you use the same license file on both, the NAV-Client you import from and on the developers toolkit.
 worked fine for me 8)0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 323 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions



