Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Friday, March 30, 2012

MSDE and Full SQL Server

This might be a stupid questions but,
Can you have a MSDE 2000 and SQL server
standard/enterprise on the same machine?
If not, can you have to instances of SQL databse with
different passwords for the 'sa' account in the respective
instances.
Many thanks
NicYou can have up to 16 instances of any edition of SQL Server 2000 (including
MSDE 2000) on a single computer.
sa is just one login that can be a member of the sysadmin fixed server role.
Any login in the sysadmin fixed server role has sys admin priviledges for
that instance of SQL Server. This would extend to any database for the
instance.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights

MSDE and Enterprise Manager

I have just installed (new clean install) of MSDE 3a. On another machine I have enterprise manager, and I thought I would be able to access it, but when I try to register it in EM it gives me the following error: SERVERNAME - SQL Server does not exist or access denied, Connection Open(Connect(). I have done this in the past with no problem. Did I forget a parameter on the install of 3a to allow other machines to access or do I have some other security issue?Depends on the configuration of MSDE. If you have enabled (using sapwd flag on setup.exe) SQL authentication, you can authenticate with these credentials. However, I did not try to connect to an MSDE instance running on another box with Enterprise Manager yet. But AFAIK, SQL auth should work fine in this case.|||I did configure it for SQL authentication.sql

MSDE and Enterprise Manager

If you have a machine running MSDE and you use Enterprise
Manager to connect to it, should you be able to set up
database maintenance plans that will delete expired
backups?
I'm seeing a situation where you can set up the
maintenance plan but the drop down box for the type of
period (days, weeks, etc) after which to delete expired
backups is blank.
My first thought is that there's an issue with using EM
to set up maintenance plans on MSDE.
Thanks for any assistance.
hi Charles,
"Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> If you have a machine running MSDE and you use Enterprise
> Manager to connect to it, should you be able to set up
> database maintenance plans that will delete expired
> backups?
> I'm seeing a situation where you can set up the
> maintenance plan but the drop down box for the type of
> period (days, weeks, etc) after which to delete expired
> backups is blank.
> My first thought is that there's an issue with using EM
> to set up maintenance plans on MSDE.
> Thanks for any assistance.
unfortunately, your first thought should be that you are not licensed to use
Enterprise Manager against MSDE instances, and you should rely on self based
solutions or third party tools
(http://www.microsoft.com/sql/msde/partners/default.asp or
http://www.aspfaq.com/show.asp?id=2442 , google for others)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for your message. My understanding of the licensing is you can use
Enterprise Manager IF you own a copy of SQL Server Standard or greater. If my
understanding is correct, then the issue goes back to functionality. Do you
agree?
In case you are wondering, you might use MSDE even if you have an installed
version of SQL Server if the application you are using is based on one or the
other. Great Plains, for example, knows which one you are using and has
specific licenses.
"Andrea Montanari" wrote:

> hi Charles,
> "Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
> news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> unfortunately, your first thought should be that you are not licensed to use
> Enterprise Manager against MSDE instances, and you should rely on self based
> solutions or third party tools
> (http://www.microsoft.com/sql/msde/partners/default.asp or
> http://www.aspfaq.com/show.asp?id=2442 , google for others)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||That's not quite correct. The Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp says the following:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
The key phrase here is "using MSDE in conjuntion with a properly licensed
copy of SQL Server 2000." Simply owning a copy of SQL Server Standard
Edition isn't enough, and you'll have to talk to your laywer to figure out
what that phrase means. All I've been told is that it doesn't apply in most
cases and requires a room full of lawyers and a white board to understand.
Rather than go through all that, you're probably better off putting Andrea's
suggestion to work and using a third-party tool.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charles Allen" <CharlesAllen@.discussions.microsoft.com> wrote in message
news:18142445-2FBB-43EC-9719-8751C5AC767D@.microsoft.com...[vbcol=seagreen]
> Thanks for your message. My understanding of the licensing is you can use
> Enterprise Manager IF you own a copy of SQL Server Standard or greater. If
> my
> understanding is correct, then the issue goes back to functionality. Do
> you
> agree?
> In case you are wondering, you might use MSDE even if you have an
> installed
> version of SQL Server if the application you are using is based on one or
> the
> other. Great Plains, for example, knows which one you are using and has
> specific licenses.
> "Andrea Montanari" wrote:
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end

Wednesday, March 28, 2012

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi,
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Data
So far so good.
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Adv
anced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem.
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to..
Thanks
dev
correction, I had installed msde using the latest sql2ksp3 exe from microsoft.
thanks
dev
|||You can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>
|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thanks
dev
|||got it, thanks
http://support.microsoft.com/default...b;en-us;823462
|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Dat
So far so good
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Advanced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to.
Thank
deYou can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thank
dev|||got it, thanks
http://support.microsoft.com/default.aspx?scid=kb;en-us;823462|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

msde 2000 sp4 - configuration failed

There is a bugfix in sp4 that I need for a customer machine. I have
been unsuccesful in getting service pack 4 installed on a test machine.
configuration:
windows 2000, msde 2000 sp2
setup command line:
setup /upgradesp sqlrun SECURITYMODE=SQL
UPGRADEUSER=myadminacct UPGRADEPWD=mypassword /L*v
C:\MSDELog.log
The setup runs for a couple minutes, then dialog progress bar winds
down. I have a 3.7 MB log, at the end I have:
=== Logging stopped: 7/7/2005 15:30:34 ===
MSI (c) (44:BC): Note: 1: 1729
MSI (c) (44:BC): Product: Microsoft SQL Server Desktop Engine --
Configuration failed.
MSI (c) (44:BC): Grabbed execution mutex.
MSI (c) (44:BC): Cleaning up uninstalled install packages, if
any exist
MSI (c) (44:BC): MainEngineThread is returning 1603
=== Verbose logging stopped: 7/7/2005 15:30:34 ===
After this happens, sqlserver agent will no longer start. I re-imaged
the machine and ran it again with the same result.
Anyone else have similar problems installing sp4? Anyone have a
solution?
Thanks!
hi,
slide@.backpacker.com wrote:
> === Logging stopped: 7/7/2005 15:30:34 ===
> MSI (c) (44:BC): Note: 1: 1729
> MSI (c) (44:BC): Product: Microsoft SQL Server Desktop Engine --
> Configuration failed.
> MSI (c) (44:BC): Grabbed execution mutex.
> MSI (c) (44:BC): Cleaning up uninstalled install packages, if
> any exist
> MSI (c) (44:BC): MainEngineThread is returning 1603
> === Verbose logging stopped: 7/7/2005 15:30:34 ===
please search for
RETURN VALUE 3
entries... about 10/15 lines before each entry you should find some
(sometime cryptic) description...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea, thanks for the response! I found a 3:
<first>
Starting custom action SetFileAndRegACLs()
Beginning modification of directory Security Descriptor (SD).
SQL Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
SQL Data Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
SQL Service Account: .\dbservice
Agent Service Account: .\dbservice
Error:
No mapping between account names and security IDs was done.
Error Code = 1332
Ending modification of directory Security Descriptor (SD).
Ending custom action SetFileAndRegACLs().
Action ended 15:30:03: InstallFinalize. Return value 3.
</first>
<second>
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (14:20): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (14:20): Error in rollback skipped. Return: 5
MSI (s) (14:20): FEATURECACHE: Entering Invalidate
MSI (s) (14:20): Unlocking Server
Action ended 15:30:33: INSTALL. Return value 3.
</second>
This last one was right after a property dump after the second one:
<third>
MSI (s) (14:20): MainEngineThread is returning 1603
MSI (c) (44:BC): Back from server. Return value: 1603
MSI (c) (44:BC): Decrementing counter to disable shutdown. If counter
>= 0, shutdown will be denied. Counter after decrement: -1
Action ended 15:30:34: INSTALL. Return value 3.
</third>
Any ideas?
-Chris
Andrea Montanari wrote:
> hi,
> slide@.backpacker.com wrote:
> please search for
> RETURN VALUE 3
> entries... about 10/15 lines before each entry you should find some
> (sometime cryptic) description...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
|||hi,
slide@.backpacker.com wrote:
> Andrea, thanks for the response! I found a 3:
> <first>
> Starting custom action SetFileAndRegACLs()
> Beginning modification of directory Security Descriptor (SD).
> SQL Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
> SQL Data Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
> SQL Service Account: .\dbservice
> Agent Service Account: .\dbservice
> Error:
> No mapping between account names and security IDs was done.
> Error Code = 1332
> Ending modification of directory Security Descriptor (SD).
> Ending custom action SetFileAndRegACLs().
> Action ended 15:30:03: InstallFinalize. Return value 3.
> </first>
unfortunately I only found information like http://tinyurl.com/cs39o , and
really do not know if can help... the answers are not very consistent, but
at the very end of the thread there's a note... perhaps...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> unfortunately I only found information like http://tinyurl.com/cs39o , and
> really do not know if can help... the answers are not very consistent, but
> at the very end of the thread there's a note... perhaps...
Thanks for the "value 3" tip. This was some problem with the account
that sqlserveragent and mssqlserver were running under. Changed to
LocalSystem and installation succeeded.

Monday, March 26, 2012

MSDE 2000 on a Windows 2000 machine

After I install MSDE on a windows 2000 machine I enable the network
protocols stop and start the server and everything works fine. When I
try to disable the network protocols I stop and start the server and it
doesn't work. I have to run SVRNETCN to see that the TCP/IP and Named
Pipes are disabled. I click ok and it tells me that the server has to
stopped and started for the changes to take effect. I stop and start
the server and the changes are in effect. Any way that I can set the
changes without having to run SVRNETCN
Thanks
hi,
johndoe17@.verizon.net wrote:
> After I install MSDE on a windows 2000 machine I enable the network
> protocols stop and start the server and everything works fine. When I
> try to disable the network protocols I stop and start the server and
> it doesn't work. I have to run SVRNETCN to see that the TCP/IP and
> Named Pipes are disabled. I click ok and it tells me that the server
> has to stopped and started for the changes to take effect. I stop
> and start the server and the changes are in effect. Any way that I
> can set the changes without having to run SVRNETCN
AFAIK the Server Network Utility writes all the necessary registry entries
to perform the network protocols changes.. you should be able to do the same
"simply" assigning the
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Su perSocketNetLib
ProtocolList = ....
registry value, but this does not seems to work, so I do think svrnetcn.exe
performs further writes...
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
|||Is there a command line option I can use to run svrnetcn without the
user interface, so that I can tell it which server to set the protocols
for?
|||hi,
johndoe17@.verizon.net wrote:
> Is there a command line option I can use to run svrnetcn without the
> user interface, so that I can tell it which server to set the
> protocols for?
perhaps via WMI, but never tried it out...
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
|||Thanks for all your help. I was able to change the value in the
registry key
"HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\S uperSocketNetLib
ProtocolList = " to 0 and everything seems to be disabled.
Thanks again.
sql

MSDE 2000 mulituser on a single computer

The installation works fine, when I restarted the machine and login as an
administrator it works fine...
But when I logon as a normal user (whitout administravie rights) its no fun
anymore.
The "SQL Server Service Manager" is blank (no server or services), but I can
fill the fields with values and the service is started but they disappear
when i restart the machine, and the MSSQLSERVER service IS started!?!
But when I enable NetworkProtocols (with "Svrnetcn.exe") it works fine for
all...
Is there any other way to solve the problem?
Where can I find Microsofts documentation about this?
/Erik Fahlstrm
hi Erik,
"Erik Fahlstrm" <erik(dot)fahlstrom(at-sign)intentia(dot)se> ha scritto nel
messaggio news:%23mA1CJ3MEHA.684@.TK2MSFTNGP09.phx.gbl...
> The installation works fine, when I restarted the machine and login as an
> administrator it works fine...
> But when I logon as a normal user (whitout administravie rights) its no
fun
> anymore.
> The "SQL Server Service Manager" is blank (no server or services), but I
can
> fill the fields with values and the service is started but they disappear
> when i restart the machine, and the MSSQLSERVER service IS started!?!
> But when I enable NetworkProtocols (with "Svrnetcn.exe") it works fine for
> all...
> Is there any other way to solve the problem?
> Where can I find Microsofts documentation about this?
> /Erik Fahlstrm
this is a known issue as
http://support.microsoft.com/default...b;EN-US;814132 reports..
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Friday, March 23, 2012

MSDE 2000 Installation Fails

I am trying to install MSDE 2000 on my WIN XP Professional machine. I have
installed it previously and uninstalled it. Now I am trying to reinstall.
Here is the error message I am receiving.
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\MICHAE~1\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
MSI (s) (8C:80) [09:58:32:977]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (8C:80) [09:58:32:977]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (8C:D8) [09:58:33:007]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI6C.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\MICHAE~1\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""
MSI (c) (F0:E8) [09:58:59:656]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (8C!B4) [09:59:09:019]: 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.
Action ended 9:59:09: InstallFinalize. Re
Mike Bacher
IST Computer Technician
"Mike Bacher" wrote:

> I am trying to install MSDE 2000 on my WIN XP Professional machine. I have
> installed it previously and uninstalled it. Now I am trying to reinstall.
> Here is the error message I am receiving.
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\MICHAE~1\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
> MSI (s) (8C:80) [09:58:32:977]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (8C:80) [09:58:32:977]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (8C:D8) [09:58:33:007]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI6C.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\MICHAE~1\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""
> MSI (c) (F0:E8) [09:58:59:656]: Font created. Charset: Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (8C!B4) [09:59:09:019]: 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.
> Action ended 9:59:09: InstallFinalize. Re
> --
> Mike Bacher
> IST Computer Technician
Also here is what my cnfgsvr tells me:
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
SQL Server configuration failed.

MSDE 2000 connectivity problem

Hi,
I have installed MSDE 2000 into my desktop machine.I can
connect from other machines to my desktop and accessing
databases using Query Analyser, Enterperise manager,
Profiler.but I didn't connect from ASP.NET application
using as "connectionstring".
Earlier it was worked.now its not working.
Send me your valuable reply ASAP.
Thanks and regards,
RafiqHow does your connection string look like?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Rafiq" <anonymous@.discussions.microsoft.com> wrote in message
news:088801c3a9ab$02032c50$a401280a@.phx.gbl...
> Hi,
> I have installed MSDE 2000 into my desktop machine.I can
> connect from other machines to my desktop and accessing
> databases using Query Analyser, Enterperise manager,
> Profiler.but I didn't connect from ASP.NET application
> using as "connectionstring".
> Earlier it was worked.now its not working.
> Send me your valuable reply ASAP.
> Thanks and regards,
> Rafiq

Wednesday, March 21, 2012

MSDE 2000 and SQL 2005 Express on the same machine

Hi I would like to ask If its possible to have installed MSDE 2000 and SQL 2005 Express on the same machine. My computer uses MSDE 2000 for one application and I would like to install SQL 2005 Express for my own application. I would like to ask it will be a problem before I install it.
thanks a lot
Martin Molnar

No, there should be no interoperability problems. You should be able to install them side-by-side.

Jens K. Suessmeyer

http://www.sqlserver2005.de

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
Me
I don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE
|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net
sql

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
--
Karl Tarbet
MCSD .net

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net

Msde 2000 - Sql 2005 Express Upgrade Issue.

Hey, This is my first time posting here but here goes nothing...

Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.

BUT.

When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.

[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.

I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.

Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?

Thanks,why would you want to upgrade from MSDE 2000 to SQL 2005 express? Microsoft has stated more than 80% of the application running on SQL 2000 will not work on SQL 2005. Why not using the same old MSDE 2000?

most probably you will need to rewrite your application to handle SQL 2005|||I spoke with the third party software company and they assure me everything will work on sql express. We wanted to switch to sql express because it had the report server stuff built in. I don't really know that much about this stuff, can the sql 2005 express reporting stuff be run on msde ?|||I am not the expert here but I will just share what I have experienced so far.

Report server is a built in feature in SQL 2005. However, it has its limitation when it comes to report designer. My personal experience, it's easy to use, but it's not acceptable by the end user. I end up writing my own long script to output the whole report to excel file.

You shall show your users instead of simply pushing them to another technology. MSDE can run well on WinXP, so why change? If you can't give yourself a good reason to change, it's better to stick to something that's working.

Remember, free stuff, doesn't come in handy :D unless your requirement is very very simple.

If the software vendor assure you that, ask them to show you how to migrate the thing over. You can always use VMware or Parallels to do all the testing before you screw up your MSDE.|||Thanks for the insight with the reporting stuff. Do you know if the report stuff from express can be used with msde?

Also, I think it's to late for me on the screwing up the msde. I removed sql express now and I have reinstalled msde, but I am getting the same error I was getting with the express. I have done a little reading and it seems like it might be a problem with remote connections. Does anyone know how to make sure remote connections are allowed in msde ?sql

msde 2000

Greetings:

I am trying to install MSDE on a local machine on port 1433.
I can't get it to install using that port it only installs using shared memory according to the logs. can someone tell me how to install it using tcp port 1433 or how to change it in the registry.
so far here are a few of the settings i am passing to the setup program.

setup INSTANCENAME=something SAPWD=something_else SECURITYMODE=SQL

i have read some of the manual but i could not find how to make this change.

thanks
BrianRfer thru MSDE readme.html file to install.

MSDE 2.0 Install Fails - Unable to disable network access

I have one super stubborn machine that I am about ready to give up and redo Windows on in order to get MSDE to install.
I am trying to install MSDE 2000 Rel A on a DELL Latitude C840 Laptop. This laptop has all Windows Updates as of 5/20/04. It has MDAC v2.8 prior to install. Virus scan and spyware scan are both clean. I am installing under local Administrator account. I also close all background processes and apps prior to install. Machine name is all caps.
Here are my execution parms: (both have same results)
setup.exe SAPWD=@.@.@.@.@.@.@.
setup.exe INSTANCENAME=@.@.@.@.@.@.@. DISABLENETWORKPROTOCOLS=1 SAPWD=@.@.@.@.@.@.@.
Installation fails and then performs a rollback. I logged the install and here is what it is reporting:
================================================== =======
.
.
MSI (s) (8C:48): Creating MSIHANDLE (239) of type 790536 for thread 1096
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action DisableNetAccess()
Error : unable to disable network access to MSDE.
Ending custom action DisableNetAccess()
Action ended 14:53:45: InstallFinalize. Return value 3.
MSI (s) (8C:48): User policy value 'DisableRollback' is 0
MSI (s) (8C:48): Machine policy value 'DisableRollback' is 0
.
.
================================================== =======
It is failing to disable network access to MSDE. I verified that all prereqs for installation (file sharing, and policy settings) are correct. I think I even tried holding my breath and standing on my head while installing with no success.
Any ideas, sympathy, or support? I have searched and searched on the net but apparantly I'm the only one with this particular installation error. Lucky Me.Ok - so I learned some more information about this machine. Apparantly it has had a lot of virus problems in the past with multiple instances of the W32.Netsky.P@.mm virus that were all "removed" with the installation of Norton Anti-Virus.
One thing I decided to try was to check the registry permissions that MSDE is trying to write as it installs. Specifically I checked the permissions on the key HKLM\Software\Microsoft\MSSQLServer and I found that no read or write permissions were set for any user. I set full control to SYTEM and Administrators using RegEdt32.
Upon another logged reinstall of MSDE I recieved a different error:
================================================== ======
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SetFileAndRegACLs()
Installation drive does not support NTFS security.
Failed to set registry security.
Ending custom action SetFileAndRegACLs().
Action ended 9:27:12: InstallFinalize. Return value 3.
MSI (s) (E4:6C): User policy value 'DisableRollback' is 0
MSI (s) (E4:6C): Machine policy value 'DisableRollback' is 0
================================================== ======
This confirms that I am on the right path, but that this registry permission problem is bigger than I thought. I am wondering if there is some default registry permission that is out of whack that affect new entries being set to no read/write permissions for all users - most likely thanks to those friendly viruses that were running rampant before I came along.
Any thoughts or ideas?|||After more investigation into this registry permission problem I discovered that the registry permissions on this computer have been severely altered. (Problably by one of the many viruses that had been present and since removed)
Permissions on the top level keys, like HKEY_LOCAL_MACHINE, were set to to "Full Control for user Everyone" with no other users defined. No wonder when the MSSQLServer key was added under Software\Microsoft the Administrator and System users were denied permissions. These keys are created to inherit permissions - and with no Administrator or SYSTEM permissions set on top level nodes it just causes havok.
I also installed Norton Anti-Virus 2004 in replace of the "other" virus scanner and it had several problems during install that were related to registry permission failures.
I am offically giving up and re-installing Windows. There is no way I will ever hope to restore the correct permissions throughout the registry.

MSDE + Restricted Accounts

I appologize if this is in the wrong place. I have MSDE 2000 installed on a
machine to be used only by the local user. It is using mixed-mode authentic
ation. The machine is running windows 2000. When I login as a Restricted Use
r that user can't start the
MQSQL Server service. An Error 5 (Access Denied) is reported. I read in the
KB before that MSDE and even accesss 2000 can not run on restricted user acc
ounts by design. I would just like a link to that KB article. I have searche
d all day for it and I can
't seem to find the right combination of keywords. Thanks so much. Most of t
he KB articles seem to be only for XP, .NET and Office 2003.The problem is that only local admins have permission to stop and start
services.
You should be able to configure the MSSQL service to start automatically,
using a limited user account.
But, as a limited user logging onto a machine, you won't have the ability
to stop and start services.
Here's a referenced to the startup account permissions.
http://www.microsoft.com/technet/pr...n/sp3sec02.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Monday, March 19, 2012

MSDE + Entreprise Manager.....again

But I thing that question has never been asked before...:-)
I use Entreprise manager to manage my MSDE on my windows XP machine.
I also have on my network a SQL Server 2000.
My problem is that I cannot add my MSDE to my Entreprise manager localted on
my SQL box.
Is this by design? Can I manage my MSDE remotely from my SQL box?
Thanks
JP
JP Breton wrote:
> But I thing that question has never been asked before...:-)
> I use Entreprise manager to manage my MSDE on my windows XP machine.
> I also have on my network a SQL Server 2000.
> My problem is that I cannot add my MSDE to my Entreprise manager localted on
> my SQL box.
> Is this by design? Can I manage my MSDE remotely from my SQL box?
> Thanks
> JP
>
Hi,
there is the option DISABLENETWORKPROTOCOLS by installing MSDE, if
DISABLENETWORKPROTOCOLS=1 you can't reach the MSDE instance remotely.
Matthias Beuder
Wenn schon Mails an diesen Account sein mssen, dann bitte mit *from NG*
im Subject. Ansonsten landet die Nachricht direkt im Trash-Ordner!
Please add *from NG* to subject, otherwise the message will be moved to
the trash directory!
http://www.beuder.de
|||thanks Mathias
"Matthias Beuder" <newsgroup.user@.beuder.de> wrote in message
news:d8bvf8$2go$1@.online.de...
> JP Breton wrote:
> Hi,
> there is the option DISABLENETWORKPROTOCOLS by installing MSDE, if
> DISABLENETWORKPROTOCOLS=1 you can't reach the MSDE instance remotely.
> --
> Matthias Beuder
> Wenn schon Mails an diesen Account sein mssen, dann bitte mit *from NG*
> im Subject. Ansonsten landet die Nachricht direkt im Trash-Ordner!
> Please add *from NG* to subject, otherwise the message will be moved to
> the trash directory!
> http://www.beuder.de

MSDE (SQL Server does not exist or access denied.)


Hi all,
I'm getting this error message when I try to connect my MSDE database from other machine using enterprise manager application. Both of the machines are WinXP SP2. I found some solution such as using 'SQLServer Network Utility' but didn't work out for me. I even can not connect my database on my computer using TCP/IP. When I connect with name, it worked fine. I already enable both TCP/IP and Named pipe protocol on the MSDE machine.
If someone has solution on that please let me know.

Thanks,
MyoDid you open the ports on the computers ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||If you have SQL Server 2005 installed on the same box as the MSDE, you need make sure SQL Browser is running. Make sure the ports (UDP/1434 and your TCP Port) are open if firewall exists. Also try file sharing between machines and make it work, otherwise NP won't work. When you use cliconfg.exe, make TCP and NP are on the client protocol lists.|||
Yes,
There is also SQL 2000 and 2005Express running together with MSDE. I already changed the port no and try to connect it. But, still didn't work out. I tried at the other machine and it works. I don't know why it still doesn't work at this machine. May be I miss some configuration. I'll try again. Thanks for the message.

Regards,
Myo|||

I have exactly the same issue. I have installed MSDE2000 on a PC with Windows XP Professional and SP2. I have tried everything to connect to another remote server and still get the same error message

I have added ports 135 and ports 445 to the firewall but again without much success. Does anyone out there have any ideas on how to get this working?

|||You will first have to determine the port that MSDE is using by starting the application Srvnetcn.exe naviagte to TCP and note that number down. After this you will have to create an exclude filter for the firewall for the application sqlservr.exe using this number and the 1434 UDP for incoming request. That should egt you started for SQL Server.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi Jens,

Many thanks for your prompt response. I have tried all your suggestions but still cannot gain access to a remote database. TCP/IP is running on port 1433, using Srvnetcn.exe to check, and I have added both the entries you have suggested to the firewall exclude lists. Any other ideas? Thanks in advance