Very Computer

Event ID: 17052

Error: 17951, Severity: 18, State: 1
2000-02-24 14:39:58.87 ods      Failed to start SQL Mail session..
Operating system error 126., The specified module could not be found

I also have another question.  When I install the SQL full version,  is
there a way that I upgrade it from trial version by supplying the serial
number and keep all current dbases or I have to backup dbases, uninstall
trial version, install full version, then restore dbases from backup?

Thanks for any reply.

Quote:> I have a SQL 7.0 trial version.  I can not start SQL mail.  I got the
> following message in the Event Viewer

> Event ID: 17052

> Error: 17951, Severity: 18, State: 1
> 2000-02-24 14:39:58.87 ods      Failed to start SQL Mail session..
> Operating system error 126., The specified module could not be found

Quote:> I also have another question.  When I install the SQL full version,  is
> there a way that I upgrade it from trial version by supplying the serial
> number and keep all current dbases or I have to backup dbases, uninstall
> trial version, install full version, then restore dbases from backup?

A. For SQL 6.5 :-

1.  One method would be to backup the databases, un-install SQL, re-install SQL
and then load the databases again.

2.  A faster method is :-

   (a)  Backup your databases first (just in case)

   (b)  Copy over all the .dll's and .exe's from the full version, over the top
of the evaluation version.

   (c)  Then from the <sql>\binn directory run the following, making sure the
case is correct

       setup /t RegistryRebuild = On

   (d)  The setup routine will now run and ask you all the normal questions.  
Answer these as you did for the 120-day eval version (putting in the same paths
etc.) and it will just update all the registry entries/icons etc.  It will
leave the databases alone.

For SQL 7.0 :-

(If you can connect to SQL then you can do the first 2, otherwise it doesn't
matter, but you'll have to create the logins again manually)

(a)  Detach your user databases (sp_detach_db)
(b)  Create a script file for all logins  (or BCP out sysxlogins)
(c)  Stop SQL Server
(d)  Backup all user database files - *.mdf/*.ndf/*.ldf
(e)  Un-install SQL Server eval
(f)  Install retail copy of SQL Server
(g)  Run script to create logins (or BCP in sysxlogins)
(h)  If user databases were deleted by un-install (they shouldn't be) then
restore from backup
(i)  Attach user databases (sp_attach_db)

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (412 entries) see

http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.sql-server.co.uk