Showing posts with label engine. Show all posts
Showing posts with label engine. Show all posts

Friday, March 30, 2012

MSDE Alternative

My company develops software that is distributed to thousands of customers. We chose MSDE as the database engine. Over the past 4 months, we have spent countless hours with customers, Microsoft, Installshield and web searches trying to resolve issues with installing MSDE. The issues seem to vary by customer and most take a great deal of support time. We understood MSDE to be a product that requires little support but in hindsight, it appears that it requires a great deal of knowledge just to get installed. We make small steps but no leaps forward.

It has come time to evaluate other products. If there is a magic bullet, I would love to hear about it. In its absence, does anyone have success to share with other products?

PhilWhen you install MSDE, be sure to also install the latest MDAC update (2.8 now I think).

I had similar problems distributing testing software to universities - a total nightmare. Insisting on the latest MDAC for all servers and clients helped tremendously.

After that, it was convincing admins to assign the proper privledges, which was akin to pulling teeth.|||Thank you for your response. Below is a list of solutions we have tried. These are the items that have at least helped. We have tried others with no success.

- Updated MDAC to most current version
- Modified the install to use MS Setup instead of Installshield Merge Modules
- Installed outside of the Installshield product
- Ensured that Print/File Sharing is installed and enabled
- Copied the contents from the CD to the hard drive and installed
- Installed MSDE with blank SA password and then changed it manually after installation
- Verified that no previous instance of MSDE or SQL Server is installed

I may have missed a couple but these give you an idea of what we have been through. We sell an inexpensive product and the product has to install without event.

Any help is greatly appreciated.

Phil|||First, let me say I have no good recommendations for you as alternatives.

I am curious as to what kinds of problems you are seeing.

Have you tried a full SQL Server install in any of the trouble spots to see if would eliviate the problems?

Our biggest problems almost always stemmed from NT permissions, once the MDAC issues were ironed out.|||Our experience falls into three major categories. First, we have customers who get to the end of the MSDE Install and it starts rolling back and will never complete and ends up leaving a mess. Next, we have customers whose install freezes in the middle of the install and they have to reboot to recover. Lastly, we have customers who appear to be installed correctly but are not able to connect to the MSDE engine.

We have also wrestled with the admin issues you talk about. However, those are generally fairly quick support calls and get resolution.

Phil|||We're just discussing the install of MSDE?

What if they have it installed already?

Does your application install it for them?

Do you do a restore of a dump?|||Have you designed your own installation of MSDE, or are you using Microsoft's installer?|||Yes, we are trying to install MSDE. Initially, we tried installing via Installshield merge modules. In late fall, at Microsoft's direction, we broke our install into three pieces. We install .NET, then MSDE (using Microsoft's installer), and then lastly our custom software. We have no problems with the components other than MSDE. If MSDE is already installed, it doesn't appear to cause issues. However, some suggested that we should clean up any prior versions. We tried that as an option with very limited success.

If I understand the restore question, we are starting from scratch.|||Sounds like the problem is Microsoft's, if it is their installer that is failing. Not much consolation, but what do they say?|||Over the past few days, we have talked to Microsoft a number of times. They are attempting to give us help at chipping away at the issues. However, they have also indicated that MSDE is closer to full SQL server than it is to a "personal" database (which was the way we interpreted much of their promotional information) for the purposes of the installation discussion.

We are working with them to try to resolve as many issues as possible and hope to build an installation to reflect that information. In the meantime, we are still investigating other alternatives. Our product stretches a bit outside the standalone environment into some network configurations. I am looking for a product that is easy to install but can go into a "light" network environment without introducing corruption.

Any ideas?|||Man, I can't tell you how much I hate saying this, but Access might actually work for you, if it is cheifly a standalone app, with occational (limited concurrent users) network use. I am dodging lightning bolts here.

Also, it is (was?) my understanding that MS planned on ditching Access/Jet for the desktop, and replace it with Access/MSDE. Are they backing off that concept now?

Plus, desktop or not, the they should (need) to get the thing to actually install without rolling itself back.

Hmm, just a thought. Could it be related in any way to XP config save points?|||Hi,

Just wanting to find out if there were any breakthroughs in consistently installing MSDE?
My company has had similar problems to what Phil described in this thread.

We've also tried all sorts of variations. Ensuring MDAC 2.8 and IE 6(!) is installed first made helped, but we still get a significant proportion of failed installs.

As with Phil, we can't afford to spend hours working with each customer to make the install work. MSDE is used with the low end (cheap) version of our software!

Regards,
Peter|||hi, i've encountered such problem dealing with MSDE installation and deployment on such environment you said. why not try the full scale MS SQL Server? 2000 i recommened 'coz it solve the problem. Another thing is i'm trying another db, (MySQL, InterBase, Adabas D and MaxDB) which are good alternatives for MSDE. but if you prefer Microsoft products, go to the full scale MS SQL Server. that should solve your problem in any ways. Hard to find that "lite" db. :(|||Full SQL2K instead of MSDE? You may degrade your workstation if you go that route. Reading MSDE prerequisites definitely gets you closer to performing a successful install.

Wednesday, March 28, 2012

MSDE 2000 SP4 Merge Modules

I have a MSDE 2000 InstallShield install package that I've created using the
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
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
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:

> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> 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
>
>

Friday, March 23, 2012

MSDE 2000 error

1. Am i right in assumeing MSDE 2000 and SQL Server 2000 Desktop engine Release A are the same.
2. Only people who have old MSDE shld install MSDE 2000 sp3 or sp3a, does that also mean for fresh insallation MSDE 2000 sp3 is enough.Frankly, at this stage I dont remember which file I downloaded but I guess it is SQL2kdesksp3.exe
3. I would like to use MSDE 2000 for VS.NET 2003 and I downloaded it from this site and followed the instructions given there:
http://www.microsoft.com/downloads/d...displaylang=en
3a. I know it is working because I see the green arrow light at the taskbar for start/stop and pausing the SQL Server
3b. I also downloaded the MS SQL Web Administrator from this site:
http://www.microsoft.com/downloads/d...displaylang=en
3c. But when I use the SQL web administrator to connet to SQL server it doesn't, but I still see the green light on the taskbar. Am I doing something wrong?
4. what is MSDE 2000 Deployment Toolkit Release Candidate - Do I need to install that also?
5. I plan to use VS.NET 2003 with MSDE 2000 - how do I test it from VS.NET? I do have the scripts for intallling Northwind database and when I use the OSQL utility I get the error as
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
SQL Server Desktop Engine Rel A *is* MSDE 2000 with SP 3a already applied,
so you don't need to install SP 3a on a Release A installation. What
login/password are you using to connect, or are you using NT Authentication?
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23PTvP4fvEHA.908@.TK2MSFTNGP11.phx.gbl...
>
> 1. Am i right in assumeing MSDE 2000 and SQL Server 2000 Desktop engine
Release A are the same.
> 2. Only people who have old MSDE shld install MSDE 2000 sp3 or sp3a, does
that also mean for fresh insallation MSDE 2000 sp3 is enough.Frankly, at
this stage I dont remember which file I downloaded but I guess it is
SQL2kdesksp3.exe
> 3. I would like to use MSDE 2000 for VS.NET 2003 and I downloaded it from
this site and followed the instructions given there:
>
http://www.microsoft.com/downloads/d...displaylang=en
> 3a. I know it is working because I see the green arrow light at the
taskbar for start/stop and pausing the SQL Server
>
> 3b. I also downloaded the MS SQL Web Administrator from this site:
>
http://www.microsoft.com/downloads/d...displaylang=en
> 3c. But when I use the SQL web administrator to connet to SQL server it
doesn't, but I still see the green light on the taskbar. Am I doing
something wrong?
>
> 4. what is MSDE 2000 Deployment Toolkit Release Candidate - Do I need to
install that also?
> 5. I plan to use VS.NET 2003 with MSDE 2000 - how do I test it from
VS.NET? I do have the scripts for intallling Northwind database and when I
use the OSQL utility I get the error as
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE 2000 error

1. Am i right in assumeing MSDE 2000 and SQL Server 2000 Desktop engine Rele
ase A are the same.
2. Only people who have old MSDE shld install MSDE 2000 sp3 or sp3a, does th
at also mean for fresh insallation MSDE 2000 sp3 is enough.Frankly, at this
stage I dont remember which file I downloaded but I guess it is SQL2kdesksp3
.exe
3. I would like to use MSDE 2000 for VS.NET 2003 and I downloaded it from th
is site and followed the instructions given there:
http://www.microsoft.com/downloads/...&displaylang=en
3a. I know it is working because I see the green arrow light at the taskbar
for start/stop and pausing the SQL Server
3b. I also downloaded the MS SQL Web Administrator from this site:
http://www.microsoft.com/downloads/...&displaylang=en
3c. But when I use the SQL web administrator to connet to SQL server it does
n't, but I still see the green light on the taskbar. Am I doing something w
rong?
4. what is MSDE 2000 Deployment Toolkit Release Candidate - Do I need to ins
tall that also?
5. I plan to use VS.NET 2003 with MSDE 2000 - how do I test it from VS.NET?
I do have the scripts for intallling Northwind database and when I use the O
SQL utility I get the error as
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.SQL Server Desktop Engine Rel A *is* MSDE 2000 with SP 3a already applied,
so you don't need to install SP 3a on a Release A installation. What
login/password are you using to connect, or are you using NT Authentication?
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23PTvP4fvEHA.908@.TK2MSFTNGP11.phx.gbl...
>
> 1. Am i right in assumeing MSDE 2000 and SQL Server 2000 Desktop engine
Release A are the same.
> 2. Only people who have old MSDE shld install MSDE 2000 sp3 or sp3a, does
that also mean for fresh insallation MSDE 2000 sp3 is enough.Frankly, at
this stage I dont remember which file I downloaded but I guess it is
SQL2kdesksp3.exe
> 3. I would like to use MSDE 2000 for VS.NET 2003 and I downloaded it from
this site and followed the instructions given there:
>
http://www.microsoft.com/downloads/... />
laylang=en
> 3a. I know it is working because I see the green arrow light at the
taskbar for start/stop and pausing the SQL Server
>
> 3b. I also downloaded the MS SQL Web Administrator from this site:
>
http://www.microsoft.com/downloads/... />
laylang=en
> 3c. But when I use the SQL web administrator to connet to SQL server it
doesn't, but I still see the green light on the taskbar. Am I doing
something wrong?
>
> 4. what is MSDE 2000 Deployment Toolkit Release Candidate - Do I need to
install that also?
> 5. I plan to use VS.NET 2003 with MSDE 2000 - how do I test it from
VS.NET? I do have the scripts for intallling Northwind database and when I
use the OSQL utility I get the error as
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.sql

Monday, March 19, 2012

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.I'm confused by your posting. Are you using MSDE or Access -- two different
databases. And, what do you have as a connection string ?
Michael D.|||Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.|||(1) What error message do you get when you are trying to connect ? Please cu
t an paste the entire message here.
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN c
onnection ?
Thanks,
Michael D.|||Have a look at this article...
http://support.microsoft.com/defaul...&product=adonet
Michael D.

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.
I'm confused by your posting. Are you using MSDE or Access -- two different databases. And, what do you have as a connection string ?
Michael D.
|||Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.
|||(1) What error message do you get when you are trying to connect ? Please cut an paste the entire message here.
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN connection ?
Thanks,
Michael D.
|||Have a look at this article...
http://support.microsoft.com/default...product=adonet
Michael D.

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.|||(1) What error message do you get when you are trying to connect ? Please cut an paste the entire message here
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN connection
Thanks
Michael D.|||Have a look at this article..
http://support.microsoft.com/default.aspx?kbid=308656&product=adone
Michael D

Monday, March 12, 2012

MSDE - Start Databases

Hello

I'm using SQL Server 2000 - 8.00.760 Desktop Engine.

When the SQL Server starts, it just start databases master, model and tempdb. The databases that I have created don't start. They just start when I connect to them for the first time.

What I can do to start my own database when the SQL Server starts?

Thank you.

All databases are opened at startup if they are attached to SQl Server. If you have switched on the autoclose option, they are in common closed (but not stopped) after the last user disconnected.

jens Suessmeyer.

http://www.sqlserver2005.de

|||I did't switched on the autoclose option - it is off, but my database just start on first use, causing a delay on my application while it starts. When it is already started, I have no delay. I need start my database when SQLServer (MSDE) starts. Is there anything to do to start my database on start of SQLServer (MSDE)?|||

The Service is autostart, but my own databases just start when I connect to them to the first time.

Is there anything to do to auto start databases?

Thanks.

|||Are you sure you are using a MSDE database not a sqlserver express database. This sounds like you are using user instances which are only available after connecting the first time. Where do you actually administer the SQL server databases ? After starting the server do you see the entries in sysdatabase tables / views using SELECT * from sysdatabases ?

HTH, Jens K. Suessmeyer.

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

I am using MSDE database. To administer SQL Server I use OSQL.

After start the server I ran SELECT * from sysdatabases. My own databases are listed.

|||If the databases are listed they should be available. use the SELECT name, mode, status,status2 from sysdatabases to check their current status. What is currently displayed ?

HTH, Jens K. Suessmeyer.

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

I have three databases. They are listed and the databases master, model, msdb and tempdb are listed too.

After start SQLServer, the SELECT results the same values for my three databases: mode = 0, status = 1073741848 and status2 = 16777216.

Here, my own databases are not started. In the first connect to the database I has a delay, because they are not started.

Then, I connect to one and the value for status changes to 24. Now, it is started.

Any idea?

MSDE - Start Databases

Hello

I'm using SQL Server 2000 - 8.00.760 Desktop Engine.

When the SQL Server starts, it just start databases master, model and tempdb. The databases that I have created don't start. They just start when I connect to them for the first time.

What I can do to start my own database when the SQL Server starts?

Thank you.

All databases are opened at startup if they are attached to SQl Server. If you have switched on the autoclose option, they are in common closed (but not stopped) after the last user disconnected.

jens Suessmeyer.

http://www.sqlserver2005.de

|||I did't switched on the autoclose option - it is off, but my database just start on first use, causing a delay on my application while it starts. When it is already started, I have no delay. I need start my database when SQLServer (MSDE) starts. Is there anything to do to start my database on start of SQLServer (MSDE)?|||

The Service is autostart, but my own databases just start when I connect to them to the first time.

Is there anything to do to auto start databases?

Thanks.

|||Are you sure you are using a MSDE database not a sqlserver express database. This sounds like you are using user instances which are only available after connecting the first time. Where do you actually administer the SQL server databases ? After starting the server do you see the entries in sysdatabase tables / views using SELECT * from sysdatabases ?

HTH, Jens K. Suessmeyer.

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

I am using MSDE database. To administer SQL Server I use OSQL.

After start the server I ran SELECT * from sysdatabases. My own databases are listed.

|||If the databases are listed they should be available. use the SELECT name, mode, status,status2 from sysdatabases to check their current status. What is currently displayed ?

HTH, Jens K. Suessmeyer.

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

I have three databases. They are listed and the databases master, model, msdb and tempdb are listed too.

After start SQLServer, the SELECT results the same values for my three databases: mode = 0, status = 1073741848 and status2 = 16777216.

Here, my own databases are not started. In the first connect to the database I has a delay, because they are not started.

Then, I connect to one and the value for status changes to 24. Now, it is started.

Any idea?