MSDE Toolkit issue with windows 98

Hello,
My 1st attempt to install .Net framework, MSDE, my application and the databases during setup (using the MSDE deployment toolkit RC) works fine on windows xp. Now when I try to do the same for windows 98 SE machine, I am able to install .Net framweork an
d MSDE, but after that during the installation I get the following error message:
"An exception occured in the OnAfterInstall event handler of DBInstaller.CustomInstaller --> Unable to access service: Operating system does not support controlling a Windows service. A service can only be controlled on Windows NT, Windows 2000, or lat
er."
It's clear that when the setup tries to start the service to create the database etc it fails. Is this a known issue. I researched on web but couldn't find anything. Any ideas.
Thanks
dev
Any ideas..

MSDE Tookit thinks MSDE is not installed when it is.

I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql

MSDE merge modules

Hi
I wonder if anyone can help. I am looking for the MSDE merge modules to use
in a .net 2003 set up and deployment module. see
http://support.microsoft.com/kb/325004/EN-US/
However I have already installed SQL server standard edition on my
development server. How do I get these MSM's to merge into my MSI? Am I
barking up the wrong tree?
Thanking you in advance for any help
Richard
Hello,
Personally, I use the last setup of msde (sql2000.msi and I launch it
from my setup with a custom action.)
With that, I don't need to use the merge modules and if a custommer want
to use SQL Server instead, I don't need to change my setup (I don't need
to install MSDE and just connect to sql server and it will work.)
I can give all the parameters to msiexec (or to the property table of
the msi).
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I wonder if anyone can help. I am looking for the MSDE merge modules to use
> in a .net 2003 set up and deployment module. see
> http://support.microsoft.com/kb/325004/EN-US/
> However I have already installed SQL server standard edition on my
> development server. How do I get these MSM's to merge into my MSI? Am I
> barking up the wrong tree?
> Thanking you in advance for any help
> Richard
>
|||Hi
I am interested in how you do this. You suggest that you can supply the
paramters to msiexec or the property table of MSI? Please can you point me
in the right direction.
After the instance has been created how do you then create the database and
insert any data?
Thank you for your help so far.
Richard
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...[vbcol=seagreen]
> Hello,
> Personally, I use the last setup of msde (sql2000.msi and I launch it from
> my setup with a custom action.)
> With that, I don't need to use the merge modules and if a custommer want
> to use SQL Server instead, I don't need to change my setup (I don't need
> to install MSDE and just connect to sql server and it will work.)
> I can give all the parameters to msiexec (or to the property table of the
> msi).
> Marc Allard
> Allcomp
> Richard Wilde wrote:
|||Hello,
Here is how I do that ...
1) Create a
property MSIExecPos
Value : msiexec
in the table property of the msi file (or the merge module)
2) Create a custom action
InstallMsde
Type : 114 (to ignore the return code because in Win98 sometimes the
return code is not 0 so you have problems).
source : MsiExecPos
Target
/i "MSDE\Sql2000.msi" /qb /l c:\msde.log
Personally, I put the full MSDE installation directory into a sub
directory MSDE so the root of my CD is cleaner
3) In the InstallUISequence (you have tu use InstallUISequence or the
installation won't work)
You add the action
InstallMsde
You can put a install condition or not
For the sequence, you put something in the end (1305 in my case).
After that, you can change the parameters of the MSDE file
In the property table, you put
REBOOT Value : ReallySuppress
to avoid a reboot prompt after the installation of MSDE
INSTANCENAME value : NameofYourInstance
I believe that it is necessary because if a custommer has already MSDE
installed, then you will run into very big problems to install your software
DISABLENETWORKPROTOCOLSValue : 0
If you don't do it, your server will only work locally.
SqlSaPwdValue : YourPassword
I think it is better to pass it directly in the custom action instead of
the property table.
Normally with that, all should be fine
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I am interested in how you do this. You suggest that you can supply the
> paramters to msiexec or the property table of MSI? Please can you point me
> in the right direction.
> After the instance has been created how do you then create the database and
> insert any data?
> Thank you for your help so far.
> Richard
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...
>
>

MSDE included as part of ASP.NET deployment package?

I need to design an asp.net application w/ and MSDE backend database that will be deployed at 50 different location (unrelated to each other). The application's deployment package needs to be downloaded from a web site on the internet. The end user locations do not have SQL2000 or MSDE...some have access.

I want to know if my deployment package can include the MSDE software? Or, can anyone offer ideas on the EASIEST way for these small offices to get MSDE installed on each of their servers so that my ASP.NET applications will connect to via ado.net.

Thanks for any ideas.I believe you can include it in your deployment package so long as its use at each location is consistent with the MSDE licensing agreement.

Appropriate uses of MSDE

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!