LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Michael DeGregory <[log in to unmask]>
Tue, 28 Mar 2006 10:10:47 -0500
text/plain (58 lines)
Thanks Nathan, We did updated to 14.5 I am going to try your suggestion. Do
you think updating to an older version (14.4) will work okay?

----- Original Message ----- 
From: "Nathan Brindle" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, March 28, 2006 9:55 AM
Subject: Re: DBMS configuration


> The SITE.EXE utility is completely separate from LISTSERV, and in
> fact I don't think we updated it for 14.5.  The 14.4 copy I have here
> works fine, at least under XP and Win2K Server.
>
> You can grab a fresh (well, 14.4) copy of it
> here:  ftp://ftp.lsoft.com/listserv/windows/TOOLS/site-intel.zip
>
> and unzip it into \LISTSERV\MAIN to see if that solves the problem.
>
> Nathan
>
> At 09:39 AM 3/28/2006 -0500, you wrote:
> >This seems to be an issue with the current build. We see the same thing
but
> >have not experienced any problems with back end communication.
> >
> >
> >~Chris
> >
> >
> >-----Original Message-----
> >From: LISTSERV site administrators' forum
> >[mailto:[log in to unmask]] On Behalf Of Michael DeGregory
> >Sent: Tuesday, March 28, 2006 9:35 AM
> >To: [log in to unmask]
> >Subject: DBMS configuration
> >
> >Good Morning,
> >
> >We are trying to set up Listserv on a new Windows server 2003 machine.
The
> >installation of Listserv and LSMTP seemed to work fine. The problem is
that
> >when configuring the Listserv advanced options using the "LISTSERV
> >Configuration" (site.exe) the "DBMS" button will not open the database
> >properties screen. The database and DSN has been set up and tested all
with
> >no problems. I even sent a test distribute from a table to see if it work
> >and it did. I don't know why that "DBMS" button won't open the database
> >configuration page. I guess everything can be configured manually in the
> >site.cfg file but I don't know why this is happening and if it is a
bigger
> >problem than it seems. I just hope nothing else if affected. Has any seen
> >this problem before?
> >
> >Thanks in advance,
> >Mike

ATOM RSS1 RSS2