powered by Jive Software

Imported Usernames and Password from another DB -- minor problems result

Hello All,

Using MS SQL 2005 Express. Ran a query that Inserted my Usernames and Passwords from another DB, along with a text values for the creationDate and modificationDate columns (’‘7/19/2007’’) which do not allow nulls. All went well. Users are able to log in and chat.

Problems arise in the Admin section. User Summary page shows total number of Users correctly but does not list them.

User Search fails for all (known good) Usernames, etc.

Client Sessions shows “Anonymous” for all logged in Users.

The exception to all problems above is for the “webmaster” account. Not sure when I created that account.

Looking through all the tables for the obvious omission of needed data has not yielded the answer!

Can anyone help??

Thanks in Advance!

Mike C.

Message was edited by: bipeman

Hi Mike,

What exactly did you insert into those date fields?

Also, do you see any stack traces in any of the logs?

daryl

Hi daryl, thanks for the reply!

I inserted a text value of 7/18/2007 in the date fields.

Here are the only entries in the SQL Server Error logs re Openfire:

2007-07-18 15:36:35.10 spid57 Starting up database ‘‘Openfire’’.

2007-07-18 15:36:35.21 spid57 Setting database option ANSI_NULL_DEFAULT to OFF for database Openfire.

2007-07-18 15:36:35.21 spid57 Setting database option ANSI_NULLS to OFF for database Openfire.

2007-07-18 15:36:35.23 spid57 Setting database option ANSI_PADDING to OFF for database Openfire.

2007-07-18 15:36:35.23 spid57 Setting database option ANSI_WARNINGS to OFF for database Openfire.

2007-07-18 15:36:35.25 spid57 Setting database option ARITHABORT to OFF for database Openfire.

2007-07-18 15:36:35.25 spid57 Starting up database ‘‘Openfire’’.

2007-07-18 15:36:35.26 spid57 Setting database option AUTO_CLOSE to OFF for database Openfire.

2007-07-18 15:36:35.28 spid57 Setting database option AUTO_CREATE_STATISTICS to ON for database Openfire.

2007-07-18 15:36:35.28 spid57 Setting database option AUTO_SHRINK to OFF for database Openfire.

2007-07-18 15:36:35.29 spid57 Setting database option AUTO_UPDATE_STATISTICS to ON for database Openfire.

2007-07-18 15:36:35.29 spid57 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database Openfire.

2007-07-18 15:36:35.31 spid57 Setting database option CURSOR_DEFAULT to GLOBAL for database Openfire.

2007-07-18 15:36:35.31 spid57 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database Openfire.

2007-07-18 15:36:35.32 spid57 Setting database option NUMERIC_ROUNDABORT to OFF for database Openfire.

2007-07-18 15:36:35.32 spid57 Setting database option QUOTED_IDENTIFIER to OFF for database Openfire.

2007-07-18 15:36:35.32 spid57 Setting database option RECURSIVE_TRIGGERS to OFF for database Openfire.

2007-07-18 15:36:35.34 spid57 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database Openfire.

2007-07-18 15:36:35.34 spid57 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database Openfire.

2007-07-18 15:36:35.34 spid57 Setting database option PARAMETERIZATION to SIMPLE for database Openfire.

2007-07-18 15:36:35.35 spid57 Setting database option READ_WRITE to ON for database Openfire.

2007-07-18 15:36:35.35 spid57 Setting database option RECOVERY to SIMPLE for database Openfire.

2007-07-18 15:36:35.35 spid57 Setting database option MULTI_USER to ON for database Openfire.

2007-07-18 15:36:35.35 spid57 Setting database option PAGE_VERIFY to CHECKSUM for database Openfire.

Message was edited by: bipeman

Hi Mike,

Do you mean you inserted the string “7/18/2007” or the ticks value like so ‘‘001171134862541’’ ?

daryl

Hi daryl,

I inserted 7/18/2007 exactly like that.

Figured that MS SQL would handle it as a date data type, which it does.

Bet Java doesn’'t though ???

Mike