MSDE Failed Install: back

Showing posts with label back. Show all posts

Friday, March 30, 2012

MSDE to SQL

When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks

Wednesday, March 28, 2012

msde sp4 autostart sqlagent and other fun

Since msde sp4 changes sqlagent to manual start, I found scm to reset
it back to automatic.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
-Service sqlserveragent -SvcStartT
ype 2
To get msde sp4 to update my default instance, I had to set sqlagent
'log on as' to Local System Account. Other wise it kept uninstalling.
Anyone know syntax to use scm to set the sqlagent log to Local System
Account and then back to my original user after install? Other means?
Needs to be script or bat happy solution.
hi Mike,
Mike wrote:
> Since msde sp4 changes sqlagent to manual start, I found scm to reset
> it back to automatic.
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
> -Service sqlserveragent -SvcStartT
> ype 2
> To get msde sp4 to update my default instance, I had to set sqlagent
> 'log on as' to Local System Account. Other wise it kept uninstalling.
> Anyone know syntax to use scm to set the sqlagent log to Local System
> Account and then back to my original user after install? Other means?
> Needs to be script or bat happy solution.
I know that sp4 changed something about the account requirements to run it's
services... the information provided in
http://support.microsoft.com/?id=283811 is no longer valid.. I'm checking
this article weekly for addendum, still with no luck...
still running my MSDE sp4 boxes under Local System too...

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

MSDE sharing on peer-to-peer network

We have a Front End/Back End database. The Back End is stored in a shared
folder on a per-to-peer network.
1. Can we use MSDE to back-end the database and have up to five users access
it from each of their workstations if we change the front-end to an Access
project using ADO?
2. If this can be done how will the performance compare? There are up to 40
tables containing up to 150MB of data.
Thanks
Terry
hi Terry,
Terry wrote:
> We have a Front End/Back End database. The Back End is stored in a
> shared folder on a per-to-peer network.
> 1. Can we use MSDE to back-end the database and have up to five users
> access it from each of their workstations if we change the front-end
> to an Access project using ADO?
you should not store SQL Server/MSDE databases in a network share, nor
should they be on a remote one..
users only needs to access MSDE, and thus data throught it's service and do
not need physical access to the database os files, both for security reasons
and technical perspective...
regarding Access/ADO, you actually do not need this path as you could go
with other model (c#/ADO.Net or whatever), but it's ok..

> 2. If this can be done how will the performance compare? There are up
> to 40 tables containing up to 150MB of data.
it dependes on your code quality and logic... avoid SELECT * FROM
myMillionTable and follow standard code quality and best practice for
database applications

you have to test your scenario...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Andrea
Thanks for the information.
I think I worded the question badly in terms of sharing - I understand where
you are coming from (I think). Can a user on, say Workstation 2 access the
data in an MSDE database on Workstation 1?
Terry
=================================
"Andrea Montanari" wrote:

> hi Terry,
> Terry wrote:
> you should not store SQL Server/MSDE databases in a network share, nor
> should they be on a remote one..
> users only needs to access MSDE, and thus data throught it's service and do
> not need physical access to the database os files, both for security reasons
> and technical perspective...
> regarding Access/ADO, you actually do not need this path as you could go
> with other model (c#/ADO.Net or whatever), but it's ok..
>
> it dependes on your code quality and logic... avoid SELECT * FROM
> myMillionTable and follow standard code quality and best practice for
> database applications

> you have to test your scenario...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Terry,
The answer is yes, giving that MSDE (SQL Server) is running on
workstation 1 (it is a program, not just a database "file") and that the
user on Workstation 2 has the necessary "rights" to access the database.
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Terry wrote:[vbcol=seagreen]
> Hello Andrea
> Thanks for the information.
> I think I worded the question badly in terms of sharing - I understand where
> you are coming from (I think). Can a user on, say Workstation 2 access the
> data in an MSDE database on Workstation 1?
> Terry
> =================================
> "Andrea Montanari" wrote:
>
sql

Monday, March 26, 2012

MSDE Replication ?

I am designing a web site which will use MSDE at the back end (on a remote hosting provider). Uers will be able to edit small amounts of data (in limited no. of tables) in the web application, whilst I will need to 'upload' much larger amounts (and differ
ent tables) on a daily basis.
My question is how to design the replication ?
a) Merge replicate the whole Db ? or ...
a) Split the database into two databases (one being the stuff that users/browsers can edit) and one being the other stuff that will be 'uploaded' and use different replication techniques for each ?
c) Any other way ?
Also, are there any limitations on replication with MSDE ?
Many Thanks
Also, is it possible to use the Enterprise Manager in the Developer Edition to manage the replication or is this in breach of the licensing ?
|||Sarah,
this article explains MSDE limitations/restrictions for use in replication,
and the licensing implications:
http://support.microsoft.com/default...;en-us;Q324992
HTH,
Paul Ibison
|||Sarah,
I'm not sure about the topology. Presumably the website uses MSDE and you
need to replicate to a separate site (lets say B)? When you say 'upload' is
this a flow of data from the website to site B or vice versa? Is there any
posibility of data both at site B and the website being changed before
synchronization? When you 'upload' the data, is this the entire table(s) or
incremental changes?
Regards,
Paul Ibison
|||Hiya Paul,
Thanks for the link.
Re the topology ...
Website is running MSDE (say A) whilst I have a (home) server which can run MSDE or Developer Edition (say B).
Small amount of data/tables (say Tables-X) are updated by web users on A.
All data/tables are updated daily by me on B (this is the 'upload' TO the website).
It is possible that data in Tables-X will have been updated at both A and B and hence will need merging.
The other data changes (excepting Tables-X) will largely be updates to column values but also added rows (particularly early on in the sites lifetime).
I'm assuming I'll do a merge replication with B being the Publisher/Distributor and A being the Subscriber. (Or can I do a Merge Replication on Tables-X and Transactional replication on everything else ?)
|||Sarah,
I agree - merge for Tables-X. You'll need to consider conflict resolution,
or partition the data according to the subscriber eg use identity ranges, so
no conflicts will arise. If the other tables are only changed in one
direction then transactional would be definitely suitable there.
HTH,
Paul Ibison
|||Brilliant! Thanks Paul! That's reassuring
... but can I use the Development Edition of Enterprise Manager to handle or will this breach the licencing ?
|||This is one for MS licensing (a phone call). For what it's worth, my guess is that it is allowed, as I know of someone who uses the evaluation edition of SQL Server for the same purposes and insists it is legal.
HTH,
Paul Ibison
|||Many Thanks for your help Paul

sql

Wednesday, March 21, 2012

MSDE on a 2k Domain Controller

I have asked this before, but it was a while back and then the project got
put on hold, and I can't find the replies - sorry.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
Keith
Anyone?
"Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> I have asked this before, but it was a while back and then the project got
> put on hold, and I can't find the replies - sorry.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>
|||A no-one responded yet...
Yes, you should be fine. One thing to consider is that your service account is now a domain account. I.e., a
potential security issue. (This is because a DC doesn't have any local accounts.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:e2TJLgDLEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Anyone?
>
> "Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> but
> the
> or
> a
>
sql

Monday, March 12, 2012

msde log file full

Getting error "msde log file is full, back up the transaction file for the database." I do not know how to clear out the log file for msde? Any help is greatly appreciated.
Thank you very much
If you need to keep your log backup sequence intact, you can
use something similar:
backup log msde
to disk = 'D:\PathToYourBackups\YourDB_Log.bak'
If you do not want to keep the log backup and can afford to
have the log sequence invalidated, you can use something
along the lines of:
backup log msde with truncate_only
For more information, refer to Backup in books online.
Additionally, if you aren't using the logs as part of your
recovery plan for the database, you can set it to simple
recovery.
-Sue
On Tue, 20 Apr 2004 17:36:04 -0700, Marion
<anonymous@.discussions.microsoft.com> wrote:

>Getting error "msde log file is full, back up the transaction file for the database." I do not know how to clear out the log file for msde? Any help is greatly appreciated.
>Thank you very much
|||Hi,
First check the recovery model for the database "MSDE". If it is FULL, you
need to backup the transaction log in frequent intervals. Otherwise
every time you will get this sort of error, even if you clear the log once.
I feel that you are using MSDE, You have to OSQL command line utility
OSQL -Usa -Ppassword -S Servername -Q"sp_helpdb MSDE"
If the recover model is FULL , then you have to Backup the transaction log
and shrink the transaction log file
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE to disk='d:\backup\dbname.trn'
go
dbcc shrinkfile('logical_log_file',truncateonly)
go
If the recovery model is SIMPLE then you do not want to schedule a
transaction log backup.
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE with truncate_only
go
dbcc shrinkfile('logical_log_file',truncateonly)
go
Note:
Logical Log file name can identified by executing:
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
use MSDE
go
sp_helpfile
(The name column contains the logical file name)
Thanks
Hari
MCDBA
"Marion" <anonymous@.discussions.microsoft.com> wrote in message
news:7C1DFCCA-9BF5-478E-B7AB-21F027A638FE@.microsoft.com...
> Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
> Thank you very much

msde log file full

Getting error "msde log file is full, back up the transaction file for the d
atabase." I do not know how to clear out the log file for msde? Any help i
s greatly appreciated.
Thank you very muchIf you need to keep your log backup sequence intact, you can
use something similar:
backup log msde
to disk = 'D:\PathToYourBackups\YourDB_Log.bak'
If you do not want to keep the log backup and can afford to
have the log sequence invalidated, you can use something
along the lines of:
backup log msde with truncate_only
For more information, refer to Backup in books online.
Additionally, if you aren't using the logs as part of your
recovery plan for the database, you can set it to simple
recovery.
-Sue
On Tue, 20 Apr 2004 17:36:04 -0700, Marion
<anonymous@.discussions.microsoft.com> wrote:

>Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
>Thank you very much|||Hi,
First check the recovery model for the database "MSDE". If it is FULL, you
need to backup the transaction log in frequent intervals. Otherwise
every time you will get this sort of error, even if you clear the log once.
I feel that you are using MSDE, You have to OSQL command line utility
OSQL -Usa -Ppassword -S Servername -Q"sp_helpdb MSDE"
If the recover model is FULL , then you have to Backup the transaction log
and shrink the transaction log file
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE to disk='d:\backup\dbname.trn'
go
dbcc shrinkfile('logical_log_file',truncateon
ly)
go
If the recovery model is SIMPLE then you do not want to schedule a
transaction log backup.
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE with truncate_only
go
dbcc shrinkfile('logical_log_file',truncateon
ly)
go
Note:
Logical Log file name can identified by executing:
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
use MSDE
go
sp_helpfile
(The name column contains the logical file name)
Thanks
Hari
MCDBA
"Marion" <anonymous@.discussions.microsoft.com> wrote in message
news:7C1DFCCA-9BF5-478E-B7AB-21F027A638FE@.microsoft.com...
> Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
> Thank you very much

Friday, March 9, 2012

MSDE installation rolls back automatically

When i try to install MSDE 1.0 .. it runs the install .. and thenautomatically uninstalls again...

I turned on the Verbose logging.. and found out the InstallSQLAgentSecurity is failing...

How can I get past this error? and what is causing it to fail? I am running the install as a local administrator on windows 2003.

ThanksAny help would be appreciated..|||There should be some other messages in the MSI log. Also, is there anything in the Windows event logs?

Don|||the event log only says that MSDE failed to install... the SQLSERVER Security agent is the first error in the log .... I will check the log again.. and post all the errors that find in it.. i can also post the file online.. if it will help...|||I can't say for sure that it'll help, but it might provide some clues.

Don

MSDE installation rollback

Hi,
I am trying to install msde as part of the installation with Live
Communications server. The installation rolls back with the following
shorten version of the log file. Any suggestions you could give me
will be helpful.
....
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (MACHINENAME,LocalSystem,87).
Action ended 11:44:27: InstallFinalize. Return value 3.
MSI (s) (38:60): User policy value 'DisableRollback' is 0
MSI (s) (38:60): Machine policy value 'DisableRollback' is 0
MSI (s) (38:60): Executing op:
Header(Signature=1397708873,Version=200,Timestamp= 827547001,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (38:60): Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (38:60): Executing op: DialogInfo(Type=1,Argument=Microsoft
SQL Server Desktop Engine)
MSI (s) (38:60): Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
backup files,CleanupTemplate=File: [1])
MSI (s) (38:60): Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop Engine,PackageName=sqlrun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4
373-BA0D-2F3635EC940C},,,InstanceType=0)
MSI (s) (38:60): Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (38:CC): Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAED.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1.LEG\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1.LEG\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
MSI (s) (38:60): Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
ActionStart(Name=InstallServices,Description=Insta lling new
services,Template=Service: [2])
MSI (s) (38:60): Executing op:
ServiceControl(,Name=MSSQL$RTC,Action=8,,)
MSI (s) (38:60): Executing op:
ServiceControl(,Name=SQLAgent$RTC,Action=8,,)
MSI (s) (38:60): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Registering type
libraries,Template=LibID: [1])
MSI (s) (38:60): Executing op:
TypeLibraryUnregister(,,FilePath=C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (38:60): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3:
2
MSI (s) (38:60): CMsiServices::ProcessTypeLibrary runs in local
context, not impersonated.
MSI (s) (38:60): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (38:60): Executing op:
TypeLibraryUnregister(,,FilePath=C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (38:60): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3:
2
MSI (s) (38:60): CMsiServices::ProcessTypeLibrary runs in local
context, not impersonated.
MSI (s) (38:60): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (38:60): Executing op:
TypeLibraryUnregister(,,FilePath=C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (38:60): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3:
2
MSI (s) (38:60): CMsiServices::ProcessTypeLibrary runs in local
context, not impersonated.
MSI (s) (38:60): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (38:60): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Updating
environment strings,Template=Name: [1], Value: [2], Action [3])
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
Manager\Environment,,)
MSI (s) (38:60): Executing op:
RegAddValue(Name=PATH,Value=#%C:\Program Files\Support
Tools\;%SystemRoot%\system32;%SystemRoot%;%SystemR oot%\System32\Wbem,)
MSI (s) (38:60): Executing op:
ActionStart(Name=DisableSqlAgent.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
ActionStart(Name=RollbackDisableSqlAgent.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
CustomActionRollback(Action=RollbackDisableSqlAgen t.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType= 1281,Source=BinaryData,Target=UndoDisableSqlAgent, )
MSI (s) (38:F0): Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAEE.tmp, Entrypoint: UndoDisableSqlAgent
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1.LEG\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1.LEG\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UndoDisableSqlAgent()
Starting custom action UpdateDisableSqlAgent()
Ending custom action UpdateDisableSqlAgent()
Ending custom action UndoDisableSqlAgent()
MSI (s) (38:60): Executing op:
ActionStart(Name=DisableNetAccess.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,,)
MSI (s) (38:60): Executing op:
ActionStart(Name=WriteRegistryValues,Description=W riting system
registry values,Template=Key: [1], Name: [2], Value: [3])
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\Application\RTC,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROG RA~1\MICROS~3\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70 .rll,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROGRA~1\MICROS~3\MSSQL$~1\Binn\RESOUR~1\1033\sqlev n70.rll,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\RTC
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\Application\SQLCTR$RTC,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#7,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROG RA~1\MICROS~3\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70 .rll,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\SQLCTR$RTC
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Language,Value=#1033,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\Tracking,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name={E07FDDA4-5A21-11d2-9DAD-00C04F79D434},,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name={6DC86044-0C71-11d3-9E18-00C04F79D434},,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\SQLServerSCP,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\M SSQL$RTC\Linkage,,BinaryType=0)
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Export,Value=
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$RTC\Linkage
3: 2
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$RTC\Linkage
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLPath,Value=C:\Program Files\Microsoft SQL
Server\80\Tools\,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\CurrentVersion,,Binary Type=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CurrentVersion,Value=8.00.194, )
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\CurrentVersion 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\SuperSocketNetLib\Tcp,,Bina ryType=0)
MSI (s) (38:60): Executing op: RegRemoveValue(Name=TcpPort,Value=0,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=TcpDynamicPorts,Value=0,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=TcpHideFlag,Value=#0,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\SuperSocketNetLib\Tcp 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\Parameters,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLArg2,Value=-lC:\Program Files\Microsoft SQL
Server\MSSQL$RTC\Data\mastlog.ldf,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLArg1,Value=-eC:\Program Files\Microsoft SQL
Server\MSSQL$RTC\LOG\ERRORLOG,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLArg0,Value=-dC:\Program Files\Microsoft SQL
Server\MSSQL$RTC\Data\master.mdf,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\Parameters 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=Software\Microsoft\MSSQLServer\Clie nt,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SharedMemoryOn,Value=#1,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\SuperSocketNetLib\Np,,Binar yType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=PipeName,Value=\\.\pipe\MSSQL$ RTC\sql\query,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\SuperSocketNetLib\Np 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server,,BinaryType=0)
MSI (s) (38:60): Executing op: RegRemoveValue(Name=SsrpActiveServer,,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=InstalledInstances,Value=
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\Setup,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLPath,Value=C:\Program Files\Microsoft SQL
Server\MSSQL$RTC\,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SQLDataRoot,Value=C:\Program Files\Microsoft SQL
Server\MSSQL$RTC\,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=ProductCode,Value={E09B48B5-E141-427A-AB0C-D3605127224A},)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=FirstStart,Value=#1,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=FeatureName,Value=SqlRun,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\RTC\Setup
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=Software\Microsoft\MSSQLServer\Clie nt\ConnectTo,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=DSQUERY,Value=DBNETLIB,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\ Client\ConnectTo 3:
2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\MSSQLServer\Clie nt\SuperSocketNetLib\Tcp,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=DefaultPort,Value=#1433,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\SuperSocketNetLib\Tcp
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Tapeloadwaittime,Value=#429496 7295,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=SetHostName,Value=#0,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Map$,,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Map#,Value=-,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Map_,Value=\,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=LoginMode,Value=#0,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=ListenOn,Value=SSMSSH70
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=DefaultLogin,Value=guest,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=AuditLevel,Value=#0,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\Service Manager,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Services,Value=MSDTC
MSI (s) (38:60): Executing op: RegAddValue(Name=Services,Value=
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Services,Value=
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Remote,Value=#1,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Default,Value=RTC,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=Action
Verify,Value=#0,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\Service Manager 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CSDVersion,Value=8.00.761,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CSDVersionNumber,Value=#768,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=SerialNumber,,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegRemoveValue(Name=RegisteredOwner,,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=CurrentVersion,Value=8.00.194, )
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\RTC\MSSQLServer\CurrentVersion 3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\M SSQL$RTC\Performance,,BinaryType=0)
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Collect,Value=CollectSQLPerfor manceData,)
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$RTC\Performance
3: 2
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Close,Value=CloseSQLPerformanc eData,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Open,Value=OpenSQLPerformanceD ata,)
MSI (s) (38:60): Executing op: RegCreateKey()
MSI (s) (38:60): Executing op:
RegRemoveValue(Name=Library,Value=C:\PROGRA~1\MICR OS~3\MSSQL$~1\Binn\sqlctr80.dll,)
MSI (s) (38:60): Executing op: RegRemoveKey()
MSI (s) (38:60): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$RTC\Performance
3: 2
MSI (s) (38:60): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\MSSQLServer\Clie nt\SuperSocketNetLib,,
....
....
Property(C): ACTION = INSTALL
=== Logging stopped: 10/19/2004 11:44:41 ===
MSI (c) (94:84): Note: 1: 1708
MSI (c) (94:84): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.
MSI (c) (94:84): Grabbed execution mutex.
MSI (c) (94:84): Cleaning up uninstalled install packages, if any
exist
MSI (c) (94:84): MainEngineThread is returning 1603
=== Verbose logging stopped: 10/19/2004 11:44:41 ===
hi,
"bigp" <bigpotatousa@.gmail.com> ha scritto nel messaggio
news:583919ed.0410191348.5e88411e@.posting.google.c om
> Hi,
> I am trying to install msde as part of the installation with Live
> Communications server. The installation rolls back with the following
> shorten version of the log file. Any suggestions you could give me
> will be helpful.
please have a look at
http://www.google.it/groups?as_q=Ins... um=100&hl=it
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
|||Hi Andrea,
Tried the resolutions from those posting, but there's no luck. Are
there any other workarounds to this problem?
Thanks,
Bigp
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:<2tmu76F204o8tU1@.uni-berlin.de>...
> hi,
> "bigp" <bigpotatousa@.gmail.com> ha scritto nel messaggio
> news:583919ed.0410191348.5e88411e@.posting.google.c om
> please have a look at
> http://www.google.it/groups?as_q=Ins... um=100&hl=it

Wednesday, March 7, 2012

MSDE Installation Error on Win9x

I am installing MSDE on win 9x machines and am having a problem. The installation aborts and the installshield unattend.iss script rolls back the installation. It seems the failure is in the cnfgsvr.exe program (based on the sqlstp.log file).

the command line that I use is:
msdex86 -s -a -f1 "c:\unattend.iss"

The log files sqlstp.log and cnfgsvr.out are included below.

I have seen some postings similar to this, but never a resolution. Any help would be appreciated...

Here are the log files...

Sqlstp.log file
~~~~~~~~~~~~~~~~~~~sqlstp.log~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
13:53:56 Begin Setup
13:53:56 7.00.623
13:53:56 Mode=Silent
13:53:56 ModeType=NORMAL
13:53:57 ValueFTS returned: 0
13:53:57 ValuePID returned: 0
13:53:57 ValueLic returned: 0
13:53:57 GetDefinitionEx returned: 0, Extended: 0x0
13:53:57 System: Windows 95
13:53:57 SQL Server ProductType: MSDE [0x4]
13:53:57 Begin Action: SetupInitialize
13:53:57 End Action SetupInitialize
13:53:57 Fixed install: 0
13:53:57 Begin Action: CheckRequirements
13:53:57 Platform ID: 0xf0000
13:53:57 Version: 4.0.67109975
13:53:57 DCOM95 has been detected.
13:53:57 File Version - C:\WINDOWS\SYSTEM\shdocvw.dll: 5.50.4134.600
13:53:57 ComputerName: JMCGUIRE1
13:53:57 User Name: cbauerle
13:53:57 Domain: JMCGUIRE1
13:53:57 OS Language: 0x409
13:53:57 End Action CheckRequirements
13:53:57 Begin Action: Detection
13:53:57 End Action Detection
13:53:57 Begin Action: ODBCLocked
13:53:57 C:\WINDOWS\TEMP\_ISTMP0.DIR\odbcinst.exe -IsLocked -Silent 1 -SourceDir C:\WINDOWS\TEMP\PFT234~1\X86\ODBC -LogFile C:\WINDOWS\sqlodbci.log
13:53:58 Process Exit Code: (-1)
13:53:58 End Action ODBCLocked
13:53:58 This combination of Package and Operating System allows a full product install.
13:53:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
13:53:58 CommonFilesDir=C:\Program Files\Common Files
13:53:58 Windows Directory=C:\WINDOWS\
13:53:58 Begin Action: ShowDialogs
13:53:58 Begin Action: DialogShowSdWelcome
13:53:58 End Action DialogShowSdWelcome
13:53:58 Begin Action: DialogShowSdLicense
13:53:58 End Action DialogShowSdLicense
13:53:58 Begin Action: DialogShowSdRegisterUserEx
13:53:58 End Action DialogShowSdRegisterUserEx
13:53:58 Begin Action: DialogShowSdSetupType
13:53:58 [SetupTypeSQL]
13:53:58 Result=302
13:53:58 szDir=C:\MSSQL7
13:53:58 final szDir=C:\MSSQL7
13:53:58 szDataDir=C:\MSSQL7
13:53:58 final szDataDir=C:\MSSQL7
13:53:58 End Action DialogShowSdSetupType
13:53:58 Begin Action: DialogShowSdComponentMult
13:53:58 End Action DialogShowSdComponentMult
13:53:58 Begin Action: DlgCpSortUnicode
13:53:58 Result=1
13:53:58 [DlgCpSortUnicode]
13:53:58 SortId=52
13:53:58 LCID=1033
13:53:58 CompStyle=196609
13:53:58 End Action DlgCpSortUnicode
13:53:58 Begin Action: DlgNetwork
13:53:58 Result=1
13:53:58 [DlgServerNetwork]
13:53:58 NetworkLibs=4095
13:53:58 TCPPort=1433
13:53:58 TCPPrxy=
13:53:58 NMPPipeName=\\.\pipe\sql\query
13:53:58 End Action DlgNetwork
13:53:58 Begin Action: DlgServices
13:53:58 [DlgServices]
13:53:58 Result=1
13:53:58 Local-Domain=3855
13:53:58 AutoStart=61455
13:53:58 End Action DlgServices
13:53:58 Begin Action: DialogShowSdStartCopy
13:53:58 End Action DialogShowSdStartCopy
13:53:58 Begin Action: DlgCPLLicense
13:53:58 End Action DlgCPLLicense
13:53:58 End Action ShowDialogs
13:53:58 Begin Action ProcessBeforeDataMove:
13:53:58 DeinstallStart returned (C:\MSSQL7): 0
13:53:58 End Action ProcessBeforeDataMove:
13:53:58 Begin Action ProcessComponentSelection:
13:53:58 End Action ProcessComponentSelection
13:53:58 Begin Action LogSelectedComponents:
13:53:58 SQLProg
13:53:58 SQLProg\SQLServr
13:53:58 SQLProg\SQLServr\Help
13:53:58 SQLProg\SQLServr\SCMDev
13:53:58 SQLProg\SQLServr\SCMDev\SCMh
13:53:58 SQLProg\SQLServr\SCMDev\SCMX86Lb
13:53:58 SQLProg\SQLServr\SCMDev\SCMALb
13:53:59 SQLProg\ReplSupp
13:53:59 SQLProg\ReplSupp\ReplSys
13:53:59 SQLProg\ReplSupp\ReplSys1
13:53:59 SQLProg\ReplSupp\RepComm
13:53:59 SQLProg\Dat
13:53:59 SQLProg\BaseSys
13:53:59 SQLProg\BaseBinn
13:53:59 Core
13:53:59 CoreSys
13:53:59 ODBC
13:53:59 OLEDB
13:53:59 CoreMisc
13:53:59 Jet
13:53:59 NetCore
13:53:59 CoreInst
13:53:59 Core1033
13:53:59 CoreIntl
13:53:59 CrMi1033
13:53:59 CrMiIntl
13:53:59 SysCore
13:53:59 VOLEDB
13:53:59 VODBC
13:53:59 CrRepCom
13:53:59 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
13:53:59 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
13:53:59 End Action LogSelectedComponents
13:54:00 SQL program folder: C:\MSSQL7
13:54:00 SQL data folder: C:\MSSQL7
13:54:00 Windows system folder: C:\WINDOWS\SYSTEM\
13:54:00 Prog req: 15751, Data req: 20447, Sys req: 4433
13:54:00 Prog avail: 792068, Data avail: 792068, Sys avail: 792068
13:54:00 Prog req vs. avail, 40631, 792068
13:54:00 Data req vs. avail, 20447, 792068
13:54:00 Sys req vs. avail, 24880, 792068
13:54:00 DisplaySystemPreReq
13:54:00 Begin Action MoveFileData:
13:54:32 End Action MoveFileData
13:54:32 Begin Action ProcessAfterDataMove:
13:54:32 DeinstallSetReference (C:\MSSQL7\sqlservr.exe) returned: 0
13:54:32 End Action ProcessAfterDataMove
13:54:32 Begin Action InstallPkgs:
13:54:32 Setup is installing Microsoft Data Access Components (MDAC) ...
13:54:32 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\mdac_typ.exe /q:a /c:"setup.exe /qtn"
13:55:44 Process Exit Code: (3010)
13:55:44 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
13:55:44 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\dtcsetup.exe /q:a /r:n
13:56:04 Process Exit Code: (0)
13:56:04 End Action InstallPkgs
13:56:04 Begin Action BuildServer:
13:56:04 SetNewPath returned: 3010
13:56:04 Path successfully updated.
13:56:04 C:\MSSQL7\binn\cnfgsvr.exe -Silent 1 -NoSampleDB 1 -SQLPath "C:\MSSQL7\" -SQLDataPath "C:\MSSQL7\" -SortID 52 -LCIDCompStyle "1033-196609" -HWND 732 -User sa -Pwd
13:58:14 Process Exit Code: (-1)
13:58:14 Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
13:58:14 Action CleanUpInstall:
13:58:14 C:\WINDOWS\TEMP\_ISTMP0.DIR\scm.exe -Silent 1 -Action 4 -Service SQLServerAgent
13:58:14 Process Exit Code: (0)
13:58:14 Installation Failed.
~~~~~~~~~~~~~~~end sqlstp.log~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

cnfgsvr.out file
~~~~~~~~~~~~~~~~~~~cnfgsvr.out~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
Starting Service ...

Connecting to Server ...

driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=.;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).

SQL Server configuration failed.
~~~~~~~~~~~~~~~end cnfgsvr.out~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I am able to easily reproduce the error with the following steps:

1. Install WIN95b
2. Install IE5.5
3. Install MDAC 2.6SP1
4. Install MSDE

MSDE does not install on a win95 machine that has MDAC installed.

If I install MSDE, then MDAC it is OK.

Any thoughts??

MSDE Install rolls back - not same as other posts

Windows Server 2003 with SP1.
I'm trying to install MSDE Release A (no previous installations of MSDE
exist on this server). Just before the "Please wait while Windows configures
Microsoft SQL Server Desktop Engine" finishes, the 'Cancel' button disappears
and the installation rolls back. No error message.
I ran setup through a command line with the logging parameter: setup.exe
/L*v "c:\msdelog.log" and found a 'Return Value 3' (the surrounding contents
shown below):
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (PEREZ2006,LocalSystem,87).
Action ended 13:05:25: InstallFinalize. Return value 3.
In addition, the following event appears in the Application Event Viewer:
Event Type:Information
Event Source:MsiInstaller
Event Category:None
Event ID:11708
Date:10/2/2006
Time:1:37:27 PM
User:PEREZDESIGN\Administrator
Computer:PEREZ2006
Description:
Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 45 30 39 42 34 38 42 {E09B48B
0008: 35 2d 45 31 34 31 2d 34 5-E141-4
0010: 32 37 41 2d 41 42 30 43 27A-AB0C
0018: 2d 44 33 36 30 35 31 32 -D360512
0020: 37 32 32 34 41 7d 7224A}
I have confirmed that the antivirus is disabled, file & printer sharing is
enabled, and the Server service is running. I am logged in as a domain Admin.
Any help is greatly appreciated!
aguilab@.networkinnovations.us
Brian Aguila
hi Brian,
Brian Aguila wrote:
>..
> I ran setup through a command line with the logging parameter:
> setup.exe /L*v "c:\msdelog.log" and found a 'Return Value 3' (the
> surrounding contents shown below):
> --
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (PEREZ2006,LocalSystem,87).
> Action ended 13:05:25: InstallFinalize. Return value 3.
> ...
> I have confirmed that the antivirus is disabled, file & printer
> sharing is enabled, and the Server service is running. I am logged
> in as a domain Admin.
are you perhaps installing MSDE in Terminal Server Application mode?
http://support.microsoft.com/default...b;en-us;317268
http://support.microsoft.com/default...b;EN-US;238162
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
|||No, ma'am, this server is not running in terminal services application mode.
"Andrea Montanari" wrote:

> hi Brian,
> Brian Aguila wrote:
> are you perhaps installing MSDE in Terminal Server Application mode?
> http://support.microsoft.com/default...b;en-us;317268
> http://support.microsoft.com/default...b;EN-US;238162
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.bizhttp://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Brian,
Brian Aguila wrote:
> No, ma'am,
sir ;D

> this server is not running in terminal services
> application mode.
try having a look at
http://www.experts-exchange.com/Data..._21114173.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply

Saturday, February 25, 2012

MSDE Install Failure

On a Win2Ksp3 server I am trying to install MSDE. However everytome the
installation nears the end and then rolls back. All I get in the log is:
Event Type:Information
Event Source:MsiInstaller
Event Category:None
Event ID:11708
Date:04/05/2004
Time:22:30:20
User:N/A
Computer:ORASERVER1
Description:
Product: Microsoft SQL Server Desktop Engine -- Installation operation
failed.
This came about after uninstalling BackupExec9.0 and attemtping a install of
BackupExec9.1 which also fails because it cannot install MSDE. Any ideas, I
cannot find much in Knowledgebase.
TIA
> This came about after uninstalling BackupExec9.0 and attemtping a
> install of BackupExec9.1 which also fails because it cannot install
> MSDE. Any ideas, I cannot find much in Knowledgebase.
> TIA
I read somebody's post on here today about how this went away if they
installed SP4.
WTH
|||was happening to me on a particular machine.
enabling file sharing service fixed it.
check msde dependencies to see if you have them all on your machine ?
Ranjeet.
<David> wrote in message news:OkREFBiMEHA.3556@.TK2MSFTNGP09.phx.gbl...
> On a Win2Ksp3 server I am trying to install MSDE. However everytome the
> installation nears the end and then rolls back. All I get in the log is:
> Event Type: Information
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11708
> Date: 04/05/2004
> Time: 22:30:20
> User: N/A
> Computer: ORASERVER1
> Description:
> Product: Microsoft SQL Server Desktop Engine -- Installation operation
> failed.
> This came about after uninstalling BackupExec9.0 and attemtping a install
of
> BackupExec9.1 which also fails because it cannot install MSDE. Any ideas,
I
> cannot find much in Knowledgebase.
> TIA
|||What is the 'file sharing service'?
and what dependencies exist?
I have upgraded to SP4 and it has mde no difference.

MSDE Install Failure

I am trying to install MSDE2 on Win2k server with SP4, as with many other
posts when I try and install it just rolls back. The error log generated
lists
Starting custom action NoRebootReplace
TempFolder Property is C:\WINNT\TEMP\
Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
NoRebootConnectRepl returned: 3
Action ended 16:53:55: InstallFinalize. Return value 3.
Action ended 16:53:55: INSTALL. Return value 3.
Does anyone know why this would be?
Many Thanks
hi Phil,
"Phil Milburn" <phil.milburn@.cmiplc.co.uk> ha scritto nel messaggio
news:OqaSZ%238pEHA.2604@.TK2MSFTNGP10.phx.gbl
> I am trying to install MSDE2 on Win2k server with SP4, as with many
> other posts when I try and install it just rolls back. The error log
> generated lists
> Starting custom action NoRebootReplace
> TempFolder Property is C:\WINNT\TEMP\
> Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
> NoRebootConnectRepl returned: 3
> Action ended 16:53:55: InstallFinalize. Return value 3.
> Action ended 16:53:55: INSTALL. Return value 3.
> Does anyone know why this would be?
> Many Thanks
are you installing on Terminal Server using Application Server Mode?
please add about 10/20 rows before and after the retun value 3 line
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

Monday, February 20, 2012

MSDE for Testing, SQL Server for Deployment...?

I'm going to be starting a web application this week. I have quite a bit of experience with Access Databases, and I've also used MySQL (back in my PHP days, thank GOD for ASP.NET).
The server we use to host our websites allows us to use SQL Server databases, so I want to move in that direction, but I'm not really sure where to start.
If I download MSDE, and start a database with it on a site I will be developing locally (on my XP box), will it be difficult for me to transfer the database (or layout of the database) to a production server running SQL Server. I know they're basically the same database, but I'm just afraid to start with an MSDE database and then get the site nearly complete, and then not know how to transfer it to a SQL Server DB.

I'm particularly interested to know if the majority of the database creation will be done through queries (similar to MySQL) because I figure if it is, then I can use the same queries to create the database on both the local and production server.

I just want to make sure that downloading MSDE will be a step in the right direction.

Perhaps links or tutorials or some information on things to watch out for as I take on this process would be so greatly appreciated.

Thanks very much.The same code that works on MSDE will work fine on SQL Server. You can use queries to create tables/views/stored procedures, or you can use Enterprise Manager or Visual Studio .NET (presuming you have the correct version - I am not sure what version is required of VS.NET to do DB work).|||Thanks for your reply douglas.reilly
Now if I am creating with queries, what's the best way to go about doing that exactly? Should I create a page that executes the query I type into a textbox? Or is there a better (probably more secure and reliable) way of doing it?

Thanks again for your help!

MSDE for replication on both ends?

We are designing an application that will use merge replication from a
wireless laptop back to a server. Plan on using MSDE on the laptops, can the
central P.C. that will be on the other end use the MSDE also, or does one of
them need to be full blown SQL Server?
Thanks,
Steve
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> We are designing an application that will use merge replication from a
> wireless laptop back to a server. Plan on using MSDE on the laptops, can
the
> central P.C. that will be on the other end use the MSDE also, or does one
of
> them need to be full blown SQL Server?
> Thanks,
> Steve
|||It can be used as a publisher or subscriber with merge replication - so it
should work for you.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> We are designing an application that will use merge replication from a
> wireless laptop back to a server. Plan on using MSDE on the laptops, can
the
> central P.C. that will be on the other end use the MSDE also, or does one
of
> them need to be full blown SQL Server?
> Thanks,
> Steve
|||Thanks for your information again Hilary.
We have some current applications with MSDE doing Merge replication back to
our servers running MS SQL. So we do have experience setting up and
maintaining it. We just had not set one up with the MSDE on both ends. You
lose having Enterprise Manager in the mix I guess, but we should be able to
plug the laptops into our network here and use Enterprise Manager from my
workstation to set up the publications and subscriptions on the laptops.
Thanks,
Steve
"Hilary Cotter" wrote:

> It can be used as a publisher or subscriber with merge replication - so it
> should work for you.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
> news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> the
> of
>
>

Friday, March 30, 2012

MSDE to SQL

MSDE to SQL

MSDE to SQL

Wednesday, March 28, 2012

msde sp4 autostart sqlagent and other fun

MSDE sharing on peer-to-peer network

Monday, March 26, 2012

MSDE Replication ?

Wednesday, March 21, 2012

MSDE on a 2k Domain Controller

Monday, March 12, 2012

msde log file full

msde log file full

Friday, March 9, 2012

MSDE installation rolls back automatically

MSDE installation rollback

Wednesday, March 7, 2012

MSDE Installation Error on Win9x

MSDE Install rolls back - not same as other posts

Saturday, February 25, 2012

MSDE Install Failure

MSDE Install Failure

Monday, February 20, 2012

MSDE for Testing, SQL Server for Deployment...?

MSDE for replication on both ends?

MSDE Failed Install

Blog Archive

About Me