SQL Power Software Forum

I try to call a command from out side but I keeping get this error on the log:

1 [main] INFO ca.sqlpower.architect.ArchitectUtils - Log4J configured successfully
56 [AWT-EventQueue-0] INFO ca.sqlpower.sql.PlDotIni - Beginning to read/merge new pl.ini data
98 [AWT-EventQueue-0] INFO ca.sqlpower.sql.PlDotIni - Finished reading file.
99 [AWT-EventQueue-0] INFO ca.sqlpower.sql.PlDotIni - Beginning to read/merge new pl.ini data
139 [AWT-EventQueue-0] INFO ca.sqlpower.sql.PlDotIni - Finished reading file.
1560 [AWT-EventQueue-0] INFO ca.sqlpower.sql.SPDataSource - Driver Class org.hsqldb.jdbcDriver loaded without exception
1930 [AWT-EventQueue-0] INFO ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl - Connected to repository database.
1941 [AWT-EventQueue-0] INFO ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl - Database product name: HSQL Database Engine
1941 [AWT-EventQueue-0] INFO ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl - Database product version: 1.8.0
1941 [AWT-EventQueue-0] INFO ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl - Database driver name: HSQL Database Engine Driver
1941 [AWT-EventQueue-0] INFO ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl - Database driver version: 1.8.0
1968 [AWT-EventQueue-0] ERROR ca.sqlpower.security.PLSecurityManager - WARNING: YOU ARE USING THE PL SECURITY MANAGER IN INSECURE MODE!!!
1971 [AWT-EventQueue-0] ERROR ca.sqlpower.security.PLUser - WARNING: YOU ARE USING THE PL USER IN INSECURE MODE!!!
2538 [AWT-EventQueue-0] INFO ca.sqlpower.sql.SPDataSource - Driver Class org.hsqldb.jdbcDriver loaded without exception

I think it related to some security issue, but I don't know how to solve the problem.

I am using sql server 2008, and I try both JDBC 2.0 and JTDS1.2.4 drive, the connections are fine.

But when I try to for example excute a new project, then the problem, both connection comes with error, my question is it is my computer problem or it is because simply sql server 2008 doesn't support.

Thanks