Hey,

Wondering if you guys are able to help out, just having random problems setting up the server using ms sql express 2016 with Service pack 3.

So i'll mention what I do in the process to install MI with MS SQLE and someone let me know if I missed anything or incorrectly set it up.

1: Download SQL 2016 express SP3 & Smss & MI V8

2: Install SQL server basic default installation

3:Enable TCP IP in sql configuration, and named pipes, change TCP IP ports from dynamic to whatever number you decide

4:open SMSS & change sql authentication to windows & sql

5:Restart PC

6: Install MI V8

7: Select MS SQL for the database and give it the password

8: Go to the Magicinfo Premium install folder, go to mssql and run those scripts to create a database, user & tables

9: Restart PC & start magicinfo(Go to its website, service should automatically start within 5min of pc booting.


So, Once i do all of this, I go to magicinfo website to sign into the admin account and add licenses, BUT It tells me wrong password. I checked the MSIINformation txt file created during installation which HAS THE PASSWORD WRITTEN, And it doesnt work. It either says an error has occured OR invalid password on anything. I've tried manually changing the passwords in the sql server ( I verified that the table was created, User is created, Database is created).

You can also change the password in the database, please find the following table
Database>magicinfo>Schemas>Public>Tables>mi_user_info_user

If you change the password details here in: $2a$10$QOrOX5IOGdQ75nv4LqWigeWA35MOLHf8NszMhl2.UfWlriNdnnAp6

That specific user will have the following password: Axk7ALQkg6


Still doesnt work. And best part is, there is no documentation on how to troubleshoot anything related to DB for MI, The installation instructions are basically everything I mentioned above.

And if I check the Conf.properties file in the conf folder in the installation directory, it says this for the wsrm connection... wtf?
wsrm.url=jdbc:postgresql://192.168.0.245:1433//192.168.0.245:1433//;serverName=magicinfo\\MSSQLSERVER;port=;databaseName=magicinfo


What is this? Why is it defaulting to using postgresql to connect to my ms sql server? Obviously not going to work as postgre is NOT installed on the server?

if i go to the magicinfoconfig editor app, (Run as admin) it says the DB port is 1...... and the IP is 0.0.0.0. I have tried setting up MI with MS SQL using MI v6, v5, v7, v8, v9 NONE of them work. Everytime I set everything up and it doesnt work, I simply format the PC and start over from fresh, Reinstall windows and then the sql and MI. Like, What am I missing. The SQL server and MI are sitting on the same pc...... Its connecting to Localhost...... I can open CMD and do the SQLCMD command to connect to the server, I'm in the database, I can also connect to the database using the magicinfo account from a remote computer.... But magicinfo cant seem to do anything. This is some of the worst software i have ever had the pleasure of working with. And i am not paying 500 euro;s for someone to install this for me. Its not  a hard task to do, it just needs better documentation on the process. because there is SOMETHING they didnt add which is required for functionality. Explain why after a fresh install it uses postgresql to connect to my microsoft sql server...................... I've done this installation at least 10 times within the last 3 days.

Howdy folks,

Total newbie here. I own a small ice cream shop in upstate New York and I have 2 Samsung OH55F screen that run Magic Info to display my menu. I use the screencon.eu service to upload my menu as it changes.

Recently, one of my screens went very dark. Not off, just very very dim. If I crouch and look at the screen at a very acute angle, I can see the content and change settings.

The other screen is working as it should. I haven’t changed any settings on the hardware. On the dim screen, eco mode is off. I’ve restarted the unit. 

We spent so much money on this units, I’m really nervous the screen is broken, but perhaps there is a setting or configuration that will bring it back to life.

I’ve moved the brightness and contrast to 100 but that’s doesn’t appear to be issue.

I have not reset to factory settings for fear of losing my configuration to screencom.eu

Any assistance or tips would be very much appreciated.

Tizen's current version of chromium is 56.xx which is very old compared to current chromium release  If you want to debug your website with tizen's chromium version, you can download it at:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html

The specific error I've received trying to run a shopify website on a samsung display was related to javascript and window.webPixelsManager.init()

PS You can find the exact version of your TV chromium browser in the settings.  With the version number, you can enter it at https://omahaproxy.appspot.com/ then download the equivalent windows/mac/linux version from the above link.

Hope this helps!

Dear Wukat,

For my understanding, only Samsung Signage players are compatible with MagicINFO.
Tizen OS runs on many Samsung products.

Please have look at all the Samsung signage products.
https://displaysolutions.samsung.com/main/index

Kind regards, Pepijn.

A company currently hosts MagicInfo V8 for us and we have some Samsung screens which are recommended for MagicInfo.

We recently purchased a Samsung TV which is connected to the network/internet and has the Tezma store, so, can we install the MagicInfo app to the TV and then link that to the MagicInfo server which is being hosted for us?    As our hosting company says no.

If not,  can we :-

Stream via the TV web browser
Stream via a Firestick with an android app

Or what is the best way to stream onto a different device?


If we can't make the solution work with different devices then I think we must rip it out and change solution. The Samsung solution seems great, but not every device we add can be Samsung MagicInfo kit. 

We get zero help and support from out MagicInfo hosting company, to be honest they seem a bit shady.  I am hoping to find out if we can work out a solution and then find a new host ASAP.

Thanks