MLServer 4 Content Manager
Documentation Coming Soon!
The Content Manager uses the native SQL Server client built into .NET. It does not use an odbc connection. The SQL client works by broadcasting a UDP packet on port 1433 and then listening for a response back from the server. The server then responds with the TCP port that it is listening on. The TCP port can be random.
Don't just open port 1433. SQL uses dynamic ports. You have to tell Windows Firewall that the "C:\Program Files\Microsoft SQL Server\MSSQL10_50.CINEMARSQL\MSSQL\Binn\sqlservr.exe" app is trusted so that any port it opens will pass. Same for MLServer.exe
If the MLServer PC is a dedicated PC and not regularly touched by humans there is no need to keep the Firewall turned on.
Content Manager talks to SQL server on port 1433. You have to tell the Windows Firewall that it is an accepted application. The other errors are associated with the path to the MLServer share. It must be a UNC path that resolves to the \MLServer folder on the server. The security permissions on the share should be that the group "Everyone" has read/write access. Either the path is incorrect or the permissions are not correct.
To open access to SQL Server when using dynamic ports:
- On the Start menu, click Run, type WF.msc, and then click OK.
- In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.
- In the Rule Type dialog box, select Program, and then click Next.
- In the Program dialog box, select This program path. Click Browse, and navigate to the instance of SQL Server that you want to access through the firewall, and then click Open. By default, SQL Server is at C:\Program Files\Microsoft *SQL Server\MSSQL10_50.CINEMARSQL\MSSQL\Binn\Sqlservr.exe. Click Next.
- In the Action dialog box, select Allow the connection, and then click Next.
- In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.
- In the Name dialog box, type a name and description for this rule, and then click Finish.
The share is used exclusively for Content Manager. It needs to know the root path to your MLServer folder. Creating the share only has to be done once. The share name is V4MLServer and it points to %ProgramFiles%\Cinemar\MLServer. The installer runs the MakeShare.bat file that is stored in the MLServer folder. If you have the server installed in a non-standard location edit the bat file and set it to the appropriate path. Then run the bat file to create the share.
When you first run Content Manager it will prompt you for this location. You need to enter the UNC path to the server in the form \\<<YOURSERVERNAME>>\V4MLserver
If you do not get the path correct then Content Manager will not save cover art and other images in the correct location.
When you install MLServer on any PC you should share that folder so that everyone on the network can access it. So if your MLServer PC name is "MyServer" you would go to the Cinemar\MLServer folder right click on the folder choose sharing and share the folder. Set the permissions on the share so that the group "everyone" has full control, (Read / Write)
Then when you see those prompts in Content manager you can browse the network and select the share. In this example you would select \\MyServer\MLServer"
On your OS you have a check box that says "Allow users to modify my files" You need to make sure you check that off or the content manager will not be able to save files in the share. Modify the share that you created to make sure it is checked off. (I'll try to add this step into the install of MLServer 4)
When you launch Content Manager verify that the connection settings are using this file share.
Then try the MusicLobby import.
The folder the MusicLobby importer is looking for is the MLServer folder where MLServer.exe 3 lives. If you are running Content Manager from the same PC as MLServer 3 then the folder is normally "C:\Program Files\MLServer". If you are running Content Manager from another PC that does not have MLServer 3 on it then you have to provide the network path to the MLServer file like \\OldMLServerPC\MLServer3ShareName.
If you have Windows XP, the V4MLShare doesn't run the access rights batch file, and access has to be set manually (if you have XP - that is). Check the server and confirm that the V4MLServer share was created and that "everyone" has read/write access. Either the share wasn't created or permissions were not set. When MLServer gets installed it leaves behind a batch file called MakeShare.bat. That's the file that gets called at the end of the install. You could run that and see if windows complains about anything.