COM Agent- Logon failure

Win 7 SP1, testing COM control with version 4.4 Build 339 with below code. I have checked to be sure logon is with domain/user syntax.
Options->Network->Remote Control is enabled with port 1097
(the COM License has been replaced by XXX)
RC = Remote_24x7.OpenSession("corp\quantid", "XXX", "WinSock", "LocalHost", "1097", "", False)
Is the license for the com control the right 'password' to pass in?)

The error I get from the com lastError is "An Error occurred during authentication"

The DEBUG log error is :
2012-04-24 11:46:36,664 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.log.DbLogAdaptor - Database: invoked
2012-04-24 11:46:43,193 [Thread-3] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Connect called corp\quantid XXX *****
2012-04-24 11:46:43,194 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 3
2012-04-24 11:46:43,195 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 6
2012-04-24 11:46:43,195 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - Method name opensession
2012-04-24 11:46:43,195 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - methodSignature LSSSS
2012-04-24 11:46:43,195 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - arguments 4
2012-04-24 11:46:43,195 [Thread-11811] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - method params [ATL002333635, corp\quantid, XXX, *****]
2012-04-24 11:46:43,195 [Thread-4] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Open session called ATL002333635 corp\quantid XXX
2012-04-24 11:46:43,195 [Thread-4] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - hasRemoteControlAccess: C:\Users\quantid\24x7Sched\userchk.exe
2012-04-24 11:46:43,291 [Thread-4] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - Logon failure: unknown user name or bad password.

I don't think so. For MP Edition that should be the actual user password. The debug log is indicating that login failed for user account corp\quantid and the error came from operation system when trying to authenticate that user.

It looks like you are running it on Windows. You should be able to see matching login failed message in Windows security event log.

The 24x7 Remote Control COM API docs state:
User The user ID that you want to use for the connection. If an empty
string is specified for the User, 24x7 Remote Control COM
automatically obtains user ID of the user logged on the computer
running 24x7 Remote Control COM.
Password Reserved. A String value. In the current version you should use
the 24x7 serial number.

Otherwise i would have to hardcode a password for the login which changes every 6 weeks.
Is there not another auth method that uses the current credentials?

The COM interface can be used with both the old legacy 24x7 Scheduler Windows Edition and with the new 24x7 Multi-platform Edition. Their internal security implementation is quite different. The legacy version manages internal users and passwords, has weak security and doesn't require passwords for remote connections. The new version closely integrates with operation system and network which is a much better method from the security point of view. The drawback, you need to use real user accounts and passwords. As with any other unattended automation processes, you should either use a special account with non-expiring password, that's typically what other people do , or you make the code to read required password from some config file or database and pass it dynamically. That stored password can be encrypted and decrypted in run-time as required.