SMART Launcher
SMART Launcher allows you to run different databases with correct NAV client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from system tray in few mouse clicks.
Database version is displayed just by pointing the mouse cursor on database or company (you can see "60200" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV Super role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
You can find this and other tools and how-to's here:
http://wedonav.com/#/experience/http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
Comments
Setting up instances means the SQL Server instance which contains your databases. Are you sure that "6.01" and "6.02" are SQL Server instance names? It's more like a version of NAV.
Here is short guide for setting the SMART Launcher:
1. Run
SMART Launcher, press right click on tray icon , run Settings;2. On Instances tab specify your SQL instance(s). Default SQL server instance name is "MSSQLSERVER", but more likely that you will have the custom name;
3. Save and close Settings, press right click on tray icon, run Refresh (it can take some time);
4. If everything is ok, by pressing right click on tray icon -> Instances -> Your Instance you will see the databases for which you have access;
5. The next step is specifying NAV clients. Run Settings again, open NAV Clients tab, and press icon. In the open file dialog select finsql.exe of your NAV client; Save settings;
6. The last step is mapping NAV Clients with database builds. Database build is displayed by pointing the mouse cursor on database or company in SMART Launcher (you can also find this information in $ndo$dbproperty table, field databaseversionno). Run Settings, open Builds tab and specify the desired build (for example 60200 is 2009 R2 32012 NAV version) in DB Version field; then select the Client Build for specified build.
7. Save Settings, run Refresh again; Now you can open the databases with build that you set. Do this settings for other NAV versions.
Here is screenshots for basic settings:
I also fixed some bugs (crash on refresh if not all settings complete). For now please download the newer version here, soon it will be updated in the download section.
SMART Launcher allows you to run different databases with correct NAV client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from system tray in few mouse clicks.
Database version is displayed just by pointing the mouse cursor on database or company (you can see "60200" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV Super role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
You can find this and other tools and how-to's here: http://wedonav.com/#/experience/
Update 22/09/2012:
Bugfixes:
- Crash of the program when settings are not completed
- Duplicated confirmation message when saving settings
http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
I'm on a Danish locale of NAV clients and get this error:
Johannes Sebastian
MB7-840,MB7-841
"[path to your nav]\finsql.exe" ntauthentication=yes, servername=[name of your sql server], database=[name of your database]
in my case for example it looks like:
"D:\Soft\NAV\6\Classic 6.0.33413\finsql.exe" ntauthentication=yes, servername=oslo, database="Cronus W1 Demo R2"
make shure that you are running the client and database on which SMART Launcher shows you the error.
Please check if everithing is ok, or you got the same error.
Next please upload somewhere your SMART Launcher's settings file (navlaunch.xml in the launcher's folder) and write here your system parameters:
Operation System version
NAV version, build
MS SQL Server version
SMART Launcher allows you to run different databases with correct NAV client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from system tray in few mouse clicks.
Database version is displayed just by pointing the mouse cursor on database or company (you can see "60200" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV Super role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
You can find this and other tools and how-to's here: http://wedonav.com/#/experience/
Update 2/11/2012:
Now it works with NAV 2013 Development Environment client
Update 22/09/2012:
Bugfixes:
- Crash of the program when settings are not completed
- Duplicated confirmation message when saving settings
http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
SMART Launcher allows you to run different databases with correct NAV client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from system tray in few mouse clicks.
Database version is displayed just by pointing the mouse cursor on database or company (you can see "60200" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV Super role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
You can find this and other tools and how-to's here: http://wedonav.com/#/experience/
Update 3/12/2012:
Bug with Deny Access option fixed. Now before removing the user from database Launcher tries to remove existing user schemas.
Update 2/11/2012:
Now it works with NAV 2013 Development Environment client
Update 22/09/2012:
Bugfixes:
- Crash of the program when settings are not completed
- Duplicated confirmation message when saving settings
http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
Thanks for the great tool \:D/ !
Did you do anything with your great tool for tagging a zup file along with launching a NAV Client?
With thanks
Thanks for the warm feedback
Currently there is no support for the zup file.
I hope it will be implemented in the next release as well as RTC support and probably some more features.
We are planning to present the new version before the NAV TechDays 2013 (7 & 8 November).
We are going to participate in the TechDays so you will be able to get first-hand information about Launcher and other SMART tools.
SMART Launcher allows you to run different databases with correct NAV Classic / RTC client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from the system tray in few mouse clicks. Database version is displayed just by pointing the mouse cursor on database or company (you can see "60220" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV SUPER role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
For the full list of features please read Help topic in the application settings.
You can find this and other tools and how-to's here: http://wedonav.com/#/experience/
http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
- added RTC and NAV13 support
- added Recent menu
- added ZUP file support
- added Help topic
- a lot of minor bugs are fixed
I hope you'll enjoy it
SMART Launcher allows you to run different databases with correct NAV Classic / RTC client. When you have a big amount of databases with different versions it becomes a real pain to remember the version, build and path to the NAV client for each database. SMART Launcher solves this problem. All you need is set patches to your NAV clients and map database versions to the clients (you can see this settings on the screenshot). After these simple settings you can run each database from the system tray in few mouse clicks. Database version is displayed just by pointing the mouse cursor on database or company (you can see "60220" on the screenshot).
Additional benefits:
- possibility to manage access to databases: grant / deny SQL dbo role and NAV SUPER role for user;
- possibility to add / remove SQL trigger which forbids database conversion;
For the full list of features please read Help topic in the application settings.
You can find this and other tools and how-to's here: http://wedonav.com/#/experience/
Version 30/10/2013
- NAV 2013 R2 is fully supported
- Several bugs with adding user to database for older versions are fixed
http://www.mibuso.com/dlinfo.asp?FileID=1466
Discuss this download here.
The tool doesn't support NAV2015 yet. It crashes and it seems it is looking for an image for NAV2015 and can't find it. Would be great if you can fix it and also think already about NAV 2016.
Other than this, it is an awesome tool.
Thanks,
Joerg
please try this one:
https://onedrive.live.com/redir?resid=F ... file%2czip
if it doesn't help could you please list steps to reproduce the issue and upload a screenshot of the error would be good as well
thanks!
This version works, at least now with the classic client and dev environment. Thanks!
I still have an issue to launch RTC clients if the files are stored on a network drive. I tried several servers and SMART Launcher always crashes. If I copy all files locally then it works. I would think it must be more an issue with my environment than an issue with SMART Launcher. What do you think?
Event log shows:
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
Stack:
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.ParseCommandLineArguments(System.String[])
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.PrepareCore()
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.Prepare()
at Microsoft.Dynamics.Nav.Client.Program.Main(System.String[])
Regards,
Joerg
You right, most likely the issue is in a network drive. I didn't test the tool with this kind of usage.
Could you please specify how your network path looks like? I'll try to reproduce it locally.
i'm trying it on Windows 10, and it always crashes when clicking on any project:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at SMART_Launcher.SysTrayApp.OnOpenCompany(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1063.1 built by: NETFXREL3STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
SMART Launcher
Assembly Version: 1.4.5760.28002
Win32 Version: 1.4.*
CodeBase: file:///C:/5/SMART%20Launcher.exe
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.