* This is the modus mailing list *
Lewis,
Okay my SQL guy is going to be out until Tuesday and I swear I almost have
it. I did everything on the Vircom How To regarding the SQL script but we
never ended up with a tblMsgCatalog or a tblRecipients table. What I ended
up doing was switching to the native mdb file for a short time and then
copying it over to the SQL machine and creating a new SQL database by first
importing the mdb and then using the Query to add the M3 .sql script. Now I
see the two tables named above but now I receive an error in the modus logs
referring to a field called NewMsg in tblMsgCatalog that cannot be null.
The exact error is as follows: ---- MODUSADM log entry made at 11/30/2003
14:58:29
Mail Store error [0xE00E03F6]:
State:23000,Native:515,Origin:[Microsoft][ODBC SQL Server Driver][SQL
Server]State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server
Driver][SQL Server]Cannot insert the value NULL into column 'NewMsg', table
'modus_sql.dbo.tblMsgCatalog'; column does not allow nulls. INSERT fails.The
statement has been terminated.
I can navigate through the SQL enterprise manager to the tblMsgCatalog table
and see the subfolders and all but one have the Null box checked and it is
the one being referenced in the error log. My question is this, there
appears to be an unchecked box where we could click the Null feature for
this field but I cannot figure out how to do it? I tried clicking the box,
double clicking the entire field, right clicking the field but nothing
yields any result. I believe I am almost there but don't know where to
change this one field.
Any help would be greatly appreciated,
Ken Grimes
----- Original Message -----
From: "Lewis Watson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 29, 2003 3:11 PM
Subject: [Modus] SQL died and is now rebuilt but needing assistance.
> * This is the modus mailing list *
>
> Sorry for giving a partial answer here and there.
>
> You need to have a database that includes two tables - tblMsgCatalog
> andtblRecipients. There is a zip file that includes a sql file that will
> create these two tables. You have to have these and once you have these
> in place try and restart ModusADM with the proper info for the ODBC
> connection to sql.
>
> As far as what user for SQL- sa generally has admin privileges for the
> entire SQL service which is overkill for a quarantine user. Go ahead and
> use sa for now. Once everything is working create a user in SQL and only
> allow enough permissions to perform the tasks that he needs for Modus.
>
> Again, sorry for the spotty help - I should have read your "what happened
> and what we have done" email the first time BEFORE responding :-)
> Thanks.
> Lewis
>
>
>
>
> ----- Original Message -----
> From: "Ken Grimes" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, November 29, 2003 1:38 PM
> Subject: [Modus] SQL died and is now rebuilt but needing assistance.
>
>
> > * This is the modus mailing list *
> >
> > Lewis,
> >
> > We had a hard-drive failure on our SQL machine and had to rebuild it.
> After
> > the failure we noticed our Sun backup machine wasn't backing up the SQL
> > databases. We have no files in quarantine currently do to this problem
> so
> > in essence we created a brand new SQL connection for the modus
> quarantine.
> > We used the How-to yesterday to get us to the point we are at now, but
> this
> > method currently gives me the error we are describing. Our SQL2000
> system
> > is on a Win2000 Advanced Server with all the latest patches, I am not
> sure
> > which version of MDAC we are using but we are using the TCPIP protocol
> and
> > not the named pipes convention?
> >
> > One thing I noticed in the How-to that I wasn't sure about was the
> reference
> > in STEP 1-J: Ensure that the specified SQL Account has enough rights to
> > read/write information from/to tables
> ("tblMsgCatalog","tblRecipients"),
> > used by the Quarantine mail store. I don't see these in the tables
> section
> > of SQL Enterprise Manager, do you think this may be the problem?
> >
> > Another thing I noticed was in the Zip file there was a mdb file, what
> is
> > that for? Did we need to import this in the SQL somewhere?
> >
> > SQL'y challenged,
> > Ken Grimes
> >
> >
> > ----- Original Message -----
> > From: "Lewis Watson" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Saturday, November 29, 2003 1:08 PM
> > Subject: [Modus] SQL died and is now rebuilt but needing assistance.
> >
> >
> > > * This is the modus mailing list *
> > >
> > > Hi Ken,
> > > Well, if you don't mind losing you current quarantine data you could
> try
> > > and rebuild the quarantine database tables.. The script will
> automatically
> > > drop and rebuild the tables used by Modus. Here's the how-to.
> > >
> > >
> >
>
http://www.vircom.com/L0g1n/Vircom_Clients/Howtos/howto/howtomodusmail_002.asp
> > >
> > > There are options in SQL to check and fix tables and I would certainly
> be
> > > concerned as to why it stopped working. However, you probably will be
> able
> > > to fix it without having to know why it happened, although it could
> happen
> > > again. My thoughts were before rebuilding the tables was to verify it
> was
> > > not just a communication problem between Modus and SQL.
> > > Good luck,
> > > Lewis
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Ken Grimes" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Saturday, November 29, 2003 12:57 PM
> > > Subject: [Modus] SQL died and is now rebuilt but needing assistance.
> > >
> > >
> > > > * This is the modus mailing list *
> > > >
> > > > Lewis,
> > > >
> > > > Everything works okay when in the native mdb, but when we move it
> back
> > > to
> > > > the SQL it has the same trouble.
> > > >
> > > > Thanks,
> > > > Ken Grimes
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Lewis Watson" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Saturday, November 29, 2003 11:37 AM
> > > > Subject: [Modus] SQL died and is now rebuilt but needing assistance.
> > > >
> > > >
> > > > > * This is the modus mailing list *
> > > > >
> > > > > Hi Ken,
> > > > > Good, so we know that SQL is able to talk the mail server and we
> know
> > > that
> > > > > your ODBC connection is good.
> > > > >
> > > > > Try this:
> > > > > Stop the Modusadm service.
> > > > > Change the quarantine settings so that it uses the Access DB
> option.
> > > > > Start the Modusadm service.
> > > > > Click on the quarantine button and see if you get any errors.
> > > > >
> > > > > If you do not get any errors....
> > > > > Stop the ModusAdm service
> > > > > Click the quarantine Database tab and configure your ODBC
> > > information.
> > > > > Start the ModusAdm service....
> > > > > Good luck,
> > > > > Lewis
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Ken Grimes" <[EMAIL PROTECTED]>
> > > > > To: <[EMAIL PROTECTED]>
> > > > > Sent: Saturday, November 29, 2003 11:11 AM
> > > > > Subject: [Modus] SQL died and is now rebuilt but needing
> assistance.
> > > > >
> > > > >
> > > > > > * This is the modus mailing list *
> > > > > >
> > > > > > Hello Lewis,
> > > > > >
> > > > > > We can go to the ODBC on the mail server and get a successful
> test
> > > to
> > > > > the
> > > > > > database machine. BTW, we are using the IP address of the
> machine
> > > and
> > > > > not
> > > > > > the machine name....I have read on the list before that this
> method
> > > was
> > > > > > preferred.
> > > > > >
> > > > > > Ken Grimes
> > > > > >
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Lewis Watson" <[EMAIL PROTECTED]>
> > > > > > To: <[EMAIL PROTECTED]>
> > > > > > Sent: Saturday, November 29, 2003 10:42 AM
> > > > > > Subject: [Modus] SQL died and is now rebuilt but needing
> assistance.
> > > > > >
> > > > > >
> > > > > > > * This is the modus mailing list *
> > > > > > >
> > > > > > > Hi Ken,
> > > > > > > For starters I have a suggestion. Open the ODBC connection you
> use
> > > to
> > > > > > > connect to SQL from the mail server and try to test it. This
> will
> > > at
> > > > > least
> > > > > > > tell you if the mail server can connect to SQL. Once we know
> this
> > > we
> > > > > can
> > > > > > > go forward.
> > > > > > > Good luck,
> > > > > > > Lewis
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Ken Grimes" <[EMAIL PROTECTED]>
> > > > > > > To: <[EMAIL PROTECTED]>
> > > > > > > Sent: Saturday, November 29, 2003 10:22 AM
> > > > > > > Subject: [Modus] SQL died and is now rebuilt but needing
> > > assistance.
> > > > > > >
> > > > > > >
> > > > > > > Hello Everyone,
> > > > > > >
> > > > > > > We had our SQL 2000 server die on us Thanksgiving day and we
> now
> > > have
> > > > > it
> > > > > > > rebuilt however we have 100's of megs worth of error logs in
> the
> > > M3
> > > > > log
> > > > > > > folders ever few hours and I cannot figure out what we are
> doing
> > > > > wrong.
> > > > > > > We have had the SQL server running since version 1.4 so we
> have
> > > > > forgotten
> > > > > > > how to or what to do to make sure all of the items in Modus
> are
> > > > > configured
> > > > > > > correctly. We went to the Vircom site and there was a "How
> To"
> > > > > describing
> > > > > > > the SQL 2000 setup for 2.x but nothing regarding the M3
> > > specifically.
> > > > > > > There was a script for the M3 quarantine which we used and we
> > > followed
> > > > > the
> > > > > > > How To for the 2.x. We edited the existing ODBC "sa" password
> in
> > > the
> > > > > mail
> > > > > > > machine because we couldn't verify what the old one was and
> > > changed it
> > > > > in
> > > > > > > Modus and the SQL server also. We also cannot view the
> quarantine
> > > as
> > > > > it
> > > > > > > gives us an error as well. Any help would be appreciated.
> BTW,
> > > all
> > > > > > > services have been stopped and restarted not just the
> modusscan
> > > and
> > > > > > > modusadmin services as stated in the Vircom "How To:".
> > > > > > >
> > > > > > > The Modus Server logs show:
> > > > > > > Mail Store error [0xE00E03E9]:
> > > > > > > State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server
> > > Driver][SQL
> > > > > > > Server]State:37000,Native:8180,Origin:[Microsoft][ODBC SQL
> Server
> > > > > > > Driver][SQL Server]Invalid object name
> > > 'tblMsgCatalog'.Statement(s)
> > > > > could
> > > > > > > not be prepared.
> > > > > > > ---- MODUSADM log entry made at 11/29/2003 09:39:54
> > > > > > >
> > > > > > > The WebMail Quarantine link provides this error:
> > > > > > > An internal error occurred. Please try again later and contact
> > > your
> > > > > ISP if
> > > > > > > the problem persists. Description : Code : &H800E03E9
> > > > > > >
> > > > > > > Thanks in advance,
> > > > > > > Ken Grimes
> > > > > > > "Officially SQL Challenged?"
> > > > > > >
> > > > > > >
> > > > > > > **
> > > > > > > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > > > > > > with the word "UNSUBSCRIBE" in the body or subject line.
> > > > > >
> > > > > >
> > > > > > **
> > > > > > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > > > > > with the word "UNSUBSCRIBE" in the body or subject line.
> > > > >
> > > > >
> > > > > **
> > > > > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > > > > with the word "UNSUBSCRIBE" in the body or subject line.
> > > >
> > > >
> > > > **
> > > > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > > > with the word "UNSUBSCRIBE" in the body or subject line.
> > >
> > >
> > > **
> > > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > > with the word "UNSUBSCRIBE" in the body or subject line.
> >
> >
> > **
> > To unsubscribe, send an Email to: [EMAIL PROTECTED]
> > with the word "UNSUBSCRIBE" in the body or subject line.
>
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.
**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.
