OpManager won't start after migration to MSSQL

This is what I have in my error logs:

06:16:54:557 AM ~~~~~~~~~~~~~~~ Logging started ~~~~~~~~~~~~~~~~
-------General Information------
Product = OpManager Version x.x
Service Pack Version =NONE
os name=Windows 2003
os version=5.2
os architecture=x86
java version=1.5.0
java vendor=Sun Microsystems Inc.
java specification=Java Platform API Specification
java specification version=1.5
java vm name=Java HotSpot(TM) Client VM
java vm information =mixed mode
java compiler=null
********************************************************

06:16:54:557 AM Messages on ********Friday, September 29, 2006********
06:16:55:194 AM -------RDBMS related information------
database product name = Microsoft SQL Server
database product version=09.00.2047
database driver name=jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
database driver version=1.2
database user name=OpManager
database URL=jdbc:jtds:sqlserver://pintlis-msdb01.dfi-intl.com:1433/OpManagerDB
******************************************************
06:17:05:755 AM No response from the Primary Server as it may not be running. Unable to connect.java.rmi.ConnectException: Connection refused to host: 172.16.101.111; nested exception is:
java.net.ConnectException: Connection refused: connect
06:17:05:755 AM Primary Server may not have been properly shutdown in the last run, resulting in the Database not being properly updated.
06:17:05:755 AM Starting up as Primary Server and correcting the Server information in the Database.
06:17:09:975 AM (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:8080

06:17:09:975 AM no listening sockets available, shutting down

06:17:09:975 AM Unable to open logs

06:17:09:975 AM

Sep 29, 2006 6:17:11 AM com.adventnet.db.persistence.metadata.MetaDataAccess createTables
INFO: Creating tables, which are not specified in DatabaseSchema.conf, for the module Persistence
Sep 29, 2006 6:17:11 AM com.adventnet.db.persistence.metadata.MetaDataAccess createTables

<snip>

06:23:24:800 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:25:264 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:25:727 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:26:191 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:26:655 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:27:119 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:27:583 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:28:047 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:28:510 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:28:974 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:29:438 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:29:902 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:30:366 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:30:829 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:31:293 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:31:757 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:32:221 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:32:685 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:33:149 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
06:23:33:612 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####

The last errors are logged continually..