Hi there!

I have been using Sam broadcaster for quite a while now and never had any major problem with it. Until today when my Sam reporter stopped working. I have always used port 3307 (mysql) and 1222 on this specific computer for Sam reporter. When I switch to 3306 it works fine, however, I need this computer to run on 3307 so not to conflict with my other one. Here is the error my sam reporter is showing:

status=err
SQL error=Could not connect to MySQL server

Everything else is working good except for sam reporter. Again my settings are: Local Server. Ports 3307, 1222, database: mysql.

If anyone has any ideas how to help me that would be great! Thanks so much!

Sounds like the config for Reporter has changed and you need to update the port there. Check the config.php in the SAMReporter/htdocs/common directory or the dbconfig.xml.php under appdata/local/spacialaudio/sambc/samreporter/htdocs

_________________
- Rob Oyler, SVS

Thanks so much for the reply! I changed thee ports there to 3307 but I'm getting the same error. I noticed that the host just says "localhost". Should I try changing that to my IP address?

no, localhost is correct. You may need to reboot after those changes to be recognized.

_________________
- Rob Oyler, SVS

I just rebooted and am getting the same error. I checked the firewall and the ports are allowed through it. I just keep getting the same error. It's so frustrating.

Do I need to have the database password in the database.config files?

The database password should be in %LOCALAPPDATA%\SpacialAudio\SAMBC\SAMReporter\htdocs\dbconfig.xml.php
The database password is not neccessarily present/correct in C:\Program Files (x86)\SpacialAudio\SAMBC\SAMReporter\htdocs\dbconfig.xml.php

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

Shop for readymade PAL scripts by countrywesterndj - Or get a custom script made by me (or others)

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

Thank you for your help. Unfortunately I'm still getting the error. I am using a very old operating system (windows XP) though the machine was barely used when I got it. Maybe sam Reporter doesn't work with windows XP. The PHP sam pages are working well and are receiving requests so that tells me I set the port up correctly. I wonder why I'm still getting the error?

Hi everyone,

I've still been trying to fix this problem. I have another question. Currently I am using port 3307 on a remote server - should it be a local server for sam reporter to work properly?

I would certainly doubt that SAM Reporter wouldn't work on XP. The included Apache and PHP binaries (bundled in the SAM Reporter executable file) are probably older than XP even in recent SAM versions, but even recent builds of Apache and PHP still support WinXP.

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

Shop for readymade PAL scripts by countrywesterndj - Or get a custom script made by me (or others)

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

Yes I have a feeling I can get it working eventually. I just need to know if it matters if I'm using Local or remote server on port 3307

Remote or local shouldn't matter unless the connection has a higher latency than the default timeout of the database library. (usually several seconds)
SAM reporter is just a standard PHP-website from 10-15 years ago. (The reporter thing hasn't seen any functional updates as far as I know. They're obviously keeping it alive, but that's it.)

You might run into problems with a too modern database (MySQL 5.7 / 8.0 and newer or MariaDB) if you're not using the latest SAM version. (And even then I'm not sure if they upgraded the database drivers for the SAM reporter websites as well)

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

Shop for readymade PAL scripts by countrywesterndj - Or get a custom script made by me (or others)

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode