Windows 2012 Server and Squeezbox Server

[zra]

Hey guys.

Im trying to migrate from windows 7 to windows 2012 server to run my squeezebox server and the driver isnt connecting. It's stuck on "wait to connect." I turned off the firewall on the server, and that didnt resolve it. It looks like the CQC server is connected on port 9090.

Anyone have any experience here?

[Dean Roddey]

Depending on how the driver is written, usually wait to connect means it opened the socket ok, but isn't getting love from the device for some reason. So presumably it got the socket connection made, and it's a configuration issue on the Squeeze side perhaps?

Which maybe is what you meant by connected on port 9000? You see that the driver has successfully opened port 9000 to the Squeeze server?

Put it into verbose mode and see if anything interesting pops up in the logs from the driver that might give us some more info.

[zra]

here is a snipit of the log

01/01 12:09:01-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'Audio1' is trying to connect to its device
}
01/01 12:09:01-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: version ?
}
01/01 12:09:01-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.3168, Status/App Status
Connect(): The socket is not currently connected
}
01/01 12:09:06-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'Audio1' is trying to connect to its device
}
01/01 12:09:06-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: version ?
}
01/01 12:09:06-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.3168, Status/App Status
Connect(): The socket is not currently connected
}

[Dean Roddey]

Looks like the server is dropping the connection almost immediately. Actually, it looks like maybe the driver isn't reporting a loss of connection, and so the socket never gets closed and re-opened, so it just keeps trying to use that socket. Otherwise, we should be seeing msgs about it getting and losing its comm resource and those aren't showing up.

Try pausing the driver, flushing the logs, then unpause it (still in verbose mode) and then take it back out of verbose again after 30 seconds or so and get a dump of that initial activity when it first tries to connect.

[zra]

01/01 13:18:50-automation, CQCServer, CIDOrbSrvWorkThread_4
{
CQCServer, CQCServer_DriverCtrl.cpp.54, Status/App Status
A request to resume driver Audio1 was received, starting operation
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3358, Status/App Status
Driver 'Audio1' is beginning initialization
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3505, Status/App Status
Driver 'Audio1' is trying to get its comm resource
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.2691, Status/App Status
Audio1.GetCommResource: Server = 10.0.1.65:9090
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
Driver 'Audio1' has its comm resource
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'Audio1' is trying to connect to its device
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: version ?
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.GetMsg: version 7.9.0
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: players 0 20
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.GetMsg: players 0 20 count:0
}
01/01 13:18:52-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.3083, Status/App Status
Audio1:Connect(): Unable to find player ID or name '00:04:20:22:9c:90'
}
01/01 13:18:52-automation, CQCRemVSrv, CQCRemVSrvGUIThread_1
{
CQCRemVSrv, CQCRemVSrv_WorkerThread.cpp.597, Failed/App Status
An exception occured in faux GUI loop of worker thread 1
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'Audio1' is trying to connect to its device
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: version ?
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.GetMsg: version 7.9.0
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.SendMsg: players 0 20
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.1406, Status/App Status
Audio1.GetMsg: players 0 20 count:0
}
01/01 13:18:57-automation, CQCServer, CQCDrv_Audio1Thread14
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.3083, Status/App Status
Audio1:Connect(): Unable to find player ID or name '00:04:20:22:9c:90'
}

[Dean Roddey]

Not sure what was going on before, but this is different. Maybe it's just not dealing with the other side dropping the connection or something. But anyway, the problem appears to be:

Audio1:Connect(): Unable to find player ID or name '00:04:20:22:9c:90'

Each time it tries to connect, it's getting that error. I assume that's a configuration thing?

[zra]

Thx Dean - That was it. I forgot that I needed to change the server address on the device. Bone head move.