I created a database for MP Studio but get an error on startup.
The database must be created by the MP Studio application during setup. It is NOT possible to use a previously created DB.
You could install a free version of SQL Server on the same computer you have installed MP Studio on, and allow MP Studio to create the database locally. You can download a free version of SQL Server via a link on this page:
Another option would be to ask your SQL Administrator to give your account temporary permissions to create a database on your shared SQL Server instance, and then remove the permissions from your account after you have allowed MP Studio to create the database.
Or your SQL Administrator could run MP Studio from your machine using their credentials, allowing it to create the database on the shared SQL Server. They could then use the MP Studio Store Administration menu to add your account as a Store Administrator to allow you to take control of the Silect Store database afterwards, allowing you to use your own account with MP Studio afterwards.
Moving the MP Studio database to a different machine
The recommended process to move the Silect Store database to a new machine is as follows:
- Create a copy of the current MP Studio database on the new server (backup on the old machine, restore to the new machine using SQL Manager).
- Log in to the old database with MP Studio
- Under Tools->Options, select the database tab, then change the connection to the new server
- Let MP Studio restart
- Re-open Tools->Options to verify the new database is being used
How do I specify an alternative SQL Server port number when specifying a Silect Store database in the startup wizard when running MP Studio for the first time?
You specify the SQL Server name in the following format in the MP Studio startup wizard:
SQL_SERVER [, PORT_NUMBER] [\INSTANCE_NAME]
So for example if your SQL Server is “sqlserver001”, and you are using port number 12345, and your instance name is “InternalApplications”, then you would specify:
Make sure that you include the comma character in between the name of the SQL Server and the port number.
Note that to be able to specify a port number and have it work with your SQL Server connection, you must make sure that your SQL Server instance supports remote connections, and that it supports use of the TCP/IP protocol, which SQL Server Express does not support by default.
I’m getting a serious error trying to launch MP Studio in a newly installed multi-user environment.
When you launch MP Studio for the first time, the application requires additional information from the MSI file in order to establish user settings. If you wish to install MP Studio for multiple users, the MP Studio MSI file must be in a folder which all of the users have access to.
How do I best avoid out-of-memory errors when working with file-based MPs?
Many transactions when dealing with file-based MPs require MP Studio to load all relevant MPs into memory. If it cannot find all of the MPs in the reference folder, it will go to your working folder and reload the MPs a second time. The best way to avoid this is to ensure that your reference folder contains all of the MPs that you will be working with as well as all of the MPs that they reference. The easiest way, of course, is to make your reference folder the same as the registered folder you are working with.
When I launch MP Studio Enterprise and select the Store button, I don’t see any folders my co-worker created. Also if I right click the top level the options such as Add Management Group and Add Project are grayed out. Why is that?
The store permissions are controlled by user roles within the store itself. If your user is not registered in the Store, you will not have access to the Store and the administration node and any existing folders will not be visible. Log in as the user who initially installed MP Studio, and add your user to a group within the store. Then, log out, and log back in as your proper user. The store should now be available.
How does MP Studio handle scripts in testing?
MP Studio runs all scripts locally, much like Operations Manager does when running “agentless” monitoring. Local and remote scripts are run on the machine running MP Studio. Many remotable scripts run correctly when run agentless, but not all. MP Studio specifically checks for and logs an error if it appears that the script will be accessing the file system since this will try to access the local file system, and not the file system on the machine being tested.
My password has changed. How does that affect MP Studio?
Many companies require users to change their passwords after a certain amount of time. If the users you specified during the Startup Wizard change their passwords, you may find that you start getting database errors while performing certain actions such as testing, or reviewing the store.
To make sure your passwords are correct, simply go to the Options dialog, and re-type the passwords for the MP Studio Database and the MP Store Database. When you hit Apply, it will verify that the login information is correct and you should no longer receive those errors.