MSDE setup errors

I am trying install MSDE on XPSP2 pro. It fails the following set of erros
in the setup log. These lines are from a non-verbose log I created while
running the setup.
Appreciate any help.
Thanks
Shishir
TempFolder is
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
Setting SqlEdition property failed
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (B4!D0) [17:39:55:781]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
I got some info on the possible causes of failure as below. Unfortunately
neither of them help.
If your machine name has lowercase characters then you may be hitting this
issue - http://support.microsoft.com/default...;en-us;Q285100
If you had a old instance of MSDE on the machine you may be hitting this
issue - http://support.microsoft.com/default...b;en-us;816499
"Shishir" wrote:

> I am trying install MSDE on XPSP2 pro. It fails the following set of erros
> in the setup log. These lines are from a non-verbose log I created while
> running the setup.
> Appreciate any help.
> Thanks
> Shishir
> TempFolder is
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> Setting SqlEdition property failed
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (B4!D0) [17:39:55:781]: Product: Microsoft SQL Server Desktop Engine
> -- Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
>
|||hi Shishir,
Shishir wrote:
> I am trying install MSDE on XPSP2 pro. It fails the following set
> of erros in the setup log. These lines are from a non-verbose log I
> created while running the setup.
>..
> Engine -- Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
this exception is sometime related to MDAC stack corruption... as no MDAC XP
sp2 refresh is available to fix it, you can only go as indicated in
http://www.macropool.com/en/download/mdac_xp_sp2.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I downloaded the repair tool and reregistered all the components. It still
fails the same way.
"Andrea Montanari" wrote:

> hi Shishir,
> Shishir wrote:
> this exception is sometime related to MDAC stack corruption... as no MDAC XP
> sp2 refresh is available to fix it, you can only go as indicated in
> http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

MSDE Question

Sorry if this is basic stuff but I'm new to MSDE and SQL.

I am running MSDE as the server.

I created a Microsoft Access Project and connected to the MSDE. Security is
set to Integrated Security.

When I try to open the database from an application I am writing I get a
login error stating the user doesn't have rights to the database. I am
logged in to the computer with administrator privledges but get the error.

I know that I have to tell the server that users have access to the database
but how do I do that if I can't gain access to the database?

Thanks,

EricI have hit this problem with sql server as well. I fixed it by
creating a server based login. that is one that requires a user name
and password. That way in the program all you need for permission is
those to fields in teh Connection String. Of course you still need to
grant that login access to the relevent dbs

MSDE package doesn't work on win 98

I created a install shield package on windows 98 using the
MSDE merge modules with vb .net. It works fine on 2000 and
xp but on windows 98 it give an ambiguous error: "Error
1723. Theres a problem with this windows installer
package. A DLL required for this installation to complete
could not be run."
This happenes as soon as I click on the msi file. Or if I
click the setup file then after a couple checks and when
setup tryes running the msi file.
Anyone have any ideas what it could be? Which dlls? Which
merge modules could be missing?
Any help would greatly appreciated. I've lost some hair
over this one.
You probably don't have any version of MDAC installed on the Win98 system.
Make MDAC a dependency of your install and install it first if needed before
going forward.
J
"MSDE" <Sebastian@.ilogic.com> wrote in message
news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
> I created a install shield package on windows 98 using the
> MSDE merge modules with vb .net. It works fine on 2000 and
> xp but on windows 98 it give an ambiguous error: "Error
> 1723. Theres a problem with this windows installer
> package. A DLL required for this installation to complete
> could not be run."
> This happenes as soon as I click on the msi file. Or if I
> click the setup file then after a couple checks and when
> setup tryes running the msi file.
> Anyone have any ideas what it could be? Which dlls? Which
> merge modules could be missing?
> Any help would greatly appreciated. I've lost some hair
> over this one.
|||The other problems we've found with Win98 are if file sharing isn't enabled
or if the Windows Family Logon is enabled.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:O3HnrMrnEHA.132@.TK2MSFTNGP09.phx.gbl...
> You probably don't have any version of MDAC installed on the Win98 system.
> Make MDAC a dependency of your install and install it first if needed
before
> going forward.
> J
> "MSDE" <Sebastian@.ilogic.com> wrote in message
> news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
TimeProtocolSrcDstApplication
Message
13:58:28UDP645521434ms-sql-m
[Service access request successful]
13:58:28TCP645532418cas[Access
Policy not found, dropping packet]
13:58:31TCP645532418cas[Access
Policy not found, dropping packet]
13:58:37TCP645532418cas[Access
Policy not found, dropping packet]
13:58:51TCP645582418cas[Access
Policy not found, dropping packet]
13:58:54TCP645582418cas[Access
Policy not found, dropping packet]
13:59:00TCP645582418cas[Access
Policy not found, dropping packet]
13:59:14TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:14TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:20UDP645521434ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:23TCP64564445ms-ds[Access
Policy not found, dropping packet]
From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE or VS.NET Problem

I recently installed a named MSDE instance and created a DB with SQLDMO. I can see the instance in VS.NET, but can't see the tables that SQLDMO created. When I rerun the script to create the tables, I get a SQL Server ODBC driver error saying the tables already exist. I have tried restarting the machine and the services, but still can't see the tables in VS.NET. The other strange thing is I also can't load data into the tables because SQLDMO says my tables are not in the Tables collection. I didn't get any errors when I originally ran the script that created my tables. When I checked the SQL log, I didn't see any errors, but also didn't see anything indicating the tables were created. Would SQL Server have logged this?

Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.

Thanks.

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE Login Problem

Hi All;
MSDE has so many complication to install and to use. So, I am facing one
problem right now. It is very frustrating right now. I created one VB.NET
application and used MSDE SP3. I am trying to install on Windows 2000
professional. There is a problem setting the SA password. To install MSDE I
am passing following parameter into
[Options]
INSTANCENAME= <instance name>
DISABLENETWORKPROTOCOLS=1
SAPWD= <password>
First thing, MSDE ignore SECURITYMODE = SQL at the time of installation and
installs in Windows Authentication. I can connect to MSDE in windows
authentication if I am using that connection string to connect to MSDE
Connection String = "(local)\<instance name> ;persist security info=True;
initial catalog= <database name> ;Trusted_Connection=True"
It is working fine if the Windows user is Administrator, if the user is a
domain user and not have Admin rights then it fails to connect.
I changed to MSDE login mode to SQL mode using RegEdit and change the Key to
Login mode = 2 which changes the mode to SQL Authentication. I reset the
service as well. Now, I am using that connection string to connect:
Connection String = "data source=(local)\<instance name>;initial
catalog=<database name> ; user id=sa ; password= <sa password which set at
the time of installation> " />
Now, it is failed to connect using sa login. It always says "Login failed
for user 'sa' "
I tried to connect to the MSDE using
osql -U sa -S <instance name>
then provide Password:
it is not connected that way as well.
I am stuck here, I want to install application at client side which is a
domain network and all the users can't be administrator to use the
application. The summary is I need to connect using SQL Authentication but it
is not setting the SA password properly which causes failing to connect. Is
there any suggestion and solution.
Thanks for your help in advance.
Essa, M. Mughal
Software Developer
Toronto, Canada
hi Essa,
Essa wrote:
> First thing, MSDE ignore SECURITYMODE = SQL at the time of
> installation and installs in Windows Authentication. I can connect to
> MSDE in windows authentication if I am using that connection string
> to connect to MSDE
I was unable to reproduce the problem... providing the SECURITYMODE=SQL
always set the MSDE instance to accept mixed authenticated connections..

> Connection String = "(local)\<instance name> ;persist security
> info=True; initial catalog= <database name> ;Trusted_Connection=True"
> It is working fine if the Windows user is Administrator, if the user
> is a domain user and not have Admin rights then it fails to connect.
and this is normal, as MSDE, at installation time, register local
administrators in the BUILTIN\Administrators WinNT group logins, but other
accounts (power users, limited users, .. ) have to be manually granted
authentication rights via a WinNT login or WinNT group login...

> I changed to MSDE login mode to SQL mode using RegEdit and change the
> Key to Login mode = 2 which changes the mode to SQL Authentication. I
> reset the service as well. Now, I am using that connection string to
> connect:
> Connection String = "data source=(local)\<instance name>;initial
> catalog=<database name> ; user id=sa ; password= <sa password which
> set at the time of installation> " />
> Now, it is failed to connect using sa login. It always says "Login
> failed for user 'sa' "
>
if the remaining part of the error is " ... not associated with a trusted
connection" then the server did not (still) accept the registry change, and
you have to stop and re-start it..
http://support.microsoft.com/default...;EN-US;q285097
else the provided password does not match the registered one... please
verify it is correct...
you can modify it accessing MSDE via a local windows admin in integrated
security mode and executing the
EXEC sp_password @.new = 'your_new_pwd_for_SA' , @.loginame = 'sa'
http://support.microsoft.com/default...;EN-US;q325003

> I am stuck here, I want to install application at client side which
> is a domain network and all the users can't be administrator to use
> the application. The summary is I need to connect using SQL
> Authentication but it is not setting the SA password properly which
> causes failing to connect. Is there any suggestion and solution.
in all my experiences,
C:\...\setup.exe SAPWD=your_pwd DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL
INSTANCENAME=YourInstanceName /L*v "c:\msdeLog.txt"
command line alwyas installed a named instance, with mixed mode
authentication, enabled network protocols, logging the installation process
to file
your setting of DISABLENETWORKPROTOCOLS=1 disables network protocols and no
remote connection will be granted (but this is another story)...
apart from this, but this is another entire story, you should not connect to
SQL Server with administrative privileges (sa login) if you really do not
need to... you should use normal privileged logins and database users, as
administrative permissions are not tailored for standard DML access, and
each user should log in with his/her own login, trusted or standard SQL
server authenticated...
please have an additional look at
http://www.sql-server-performance.co...l_security.asp
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
or, at least, an application role,
http://www.databasejournal.com/featu...le.php/3363521 ...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE log created?

If a /L parameter is not specified for an MSDE installation, is there
any install log created?hi,
swyck wrote:
> If a /L parameter is not specified for an MSDE installation, is there
> any install log created?
nope..
MSDE setup requires the
/L*v "c:\LogFileName.txt"
parameter in order to verbosely log the installation..
\Program Files\Microsoft SQL Server\MSSQL\Install\cnfgsvr.out
restricted log file is generated resulting like (hopefully, if correctly
installed)
"SQL Server has been correctly configured!"
regards
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
-- remove DMO to reply

MSDE Install roll-back

Downloading and running "sql2kdesksp3.exe" worked with no problems.

But running the setup program that was created has proved less successful no matter what options I specify. The installation starts but moments from completion the progress bar begins moving backward. No error message is displayed and the installation dialog simply closes.

Looking in the 'Program Files' directly during the installation shows a SQL directly but this directory is deleted before the installation dialog closes.

I've installed 'ASP.NET Web Matrix'.

What is causing the installation to rollback? Is this a licensing issue?

Some of my attempts so far:

setup SAPWD=hello SecurityMode=SQL

setup SAPWD=hello

setup SAPWD=hello INSTANCENAME=sqlstarterkitThe documentaion SUCKS for beginners (like me). I got it to work after giving the ASP.NET Machine user admin privlages, but who knows if that was the issue. I also setup using similar lines that you did.

In my search for an answer, it seems MANY people have this problem, and no one seems willing to give an answer, or a newbie-friendly how-to.

Good luck,

mikeP|||I'm in the same boat

I get the same rollback response after following the installation instructions.

Although the very 1st time I installed it, I did get a little further with the installation. I was
able to restart and was able to see the the little computer icon (with a flashing green light) located on my desktop toolbar at the botton of the screen, that said (SQL Running) when you placed the the mouse pointer over it.

Next I open up the web Matrix and proceeded to create a Database which was almost successful untill I received the following Message:

Unable to connect to the database server.
Login failed for user 'SA' Reason:
Not assoicated with a trusted SQL Server connection.

So next I thought I would uninstall & Reinstall & try again to see if I would have better luck the 2nd time. But Now each time that I have tried to reinstall MSDE "sql2kdesksp3.exe" &
follow the same installation procedure, I'm only able to get as far as Command prompt
setup and installation, then I get the same installation rollback same as what you descibed.

I also wish someone if anybody has any advice it would be greatly appreciated.

MSDE HELP

Hi,
I have 2 PCs that aren't in any domain.
One of PCs, have installed on MSDE. I change the authentication
mode from windows to mixed mode.
Created users inside MSDE.
In the PC with MSDE I can enter with all users, but in the other PC I could
not connect to the server.
I tried to register in Enterprise Manager that MSDE instalation and I get
the following error
SQL Server Enterprise Manager
SQL Server registration failed because of the connection failure displayed
below. Do you wish to Register anyway?
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes No
I already add the TCP 1433 and UDP 1434 ports to windows firewal, I tried to
with the firewall disconected and i get always the same error.
So I think the problem could be in permissions, but how can I set permisons
in one computer to a user from another computer. Don't forget that the pcs
aren't in any domain.
Or how can I put on PC connecting to the MSDE in the other PC?
thanks
Mestre
hi Mestre,
Mestre wrote:
> Hi,
> I have 2 PCs that aren't in any domain.
> One of PCs, have installed on MSDE. I change the authentication
> mode from windows to mixed mode.
> Created users inside MSDE.
> In the PC with MSDE I can enter with all users, but in the other PC I
> could not connect to the server.
> I tried to register in Enterprise Manager that MSDE instalation and I
> get the following error
> --
> SQL Server Enterprise Manager
> --
> SQL Server registration failed because of the connection failure
> displayed below. Do you wish to Register anyway?
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> --
> Yes No
> --
>
> I already add the TCP 1433 and UDP 1434 ports to windows firewal, I
> tried to with the firewall disconected and i get always the same
> error.
> So I think the problem could be in permissions, but how can I set
> permisons in one computer to a user from another computer. Don't
> forget that the pcs aren't in any domain.
> Or how can I put on PC connecting to the MSDE in the other PC?
please have a look at
http://support.microsoft.com/default...06&Product=sql
for the most common causes of this exception.. and of course please verify
that remote access to the instance is enabled with the Server Network
Utility (svrnetcn.exe) as MSDE installs by default disabling all network
protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
you're right. I discover that, but I ony have time to update the posts
today.
Thanks,
Mestre
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4271egF1hrbv5U1@.individual.net...
> hi Mestre,
> Mestre wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for the most common causes of this exception.. and of course please verify
> that remote access to the instance is enabled with the Server Network
> Utility (svrnetcn.exe) as MSDE installs by default disabling all network
> protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>