Component database server problems

[DPM]

I did something really dumb - I had a partition with XP and the XPe toolset
installed, then installed 2000 Server on the same partition (I know, I
know...). Interestingly, I can boot both! But when I boot XP although the
MSDE server is apparently running (icon in system tray is green and blinks
every few seconds) all of the tools (TD, CDM, CD) report that they are
unable to connect to it.

Now, I have 3 questions:

1. Can anyone suggest what I broke that prevents the tools from seeing the
server and what I should do to fix it?
2. Is it possible to install the tools and database on another machine and
then just copy my custom repositories, or do I have to re-import the .sld
files into the new database?
3. Is it possible to install the MSDE server and component database on one
machine and access it with tools installed on another?

Thanks for your insight.

 

[Brad Combs]

Hi Dean,

1. Can anyone suggest what I broke that prevents the tools from seeing the
server and what I should do to fix it?

I would open Component Database Manager check the "Database" tab to see if
the "Database Server Location" is the machine name of the system where MSDE
is installed. If it is different try clicking "Change" and filling in the
correct information. Also, if you change the name make sure to hit the
"Repository" tab and checking that all the repository locations are valid
(i.e. they should be a path on the local machine or a network path like
\\servername\repositories...).

2. Is it possible to install the tools and database on another machine and
then just copy my custom repositories, or do I have to re-import the .sld
files into the new database?

The SLD import process makes a record of the component in the database so
you will have to reimport your custom SLD's if you go this route.

3. Is it possible to install the MSDE server and component database on one
machine and access it with tools installed on another?

It's definitely possible to install on a network server although for
performance reasons I would suggest against it. Here is a link to installing
on the network. Follow item number 9.
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp

To install MSDE and the Component Database:
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp

HTH,
Brad

 

[DPM]

Brad,

Thanks for responding - comments below..

Hi Dean,


I would open Component Database Manager check the "Database" tab to see if
the "Database Server Location" is the machine name of the system where MSDE
is installed. If it is different try clicking "Change" and filling in the
correct information. Also, if you change the name make sure to hit the
"Repository" tab and checking that all the repository locations are valid
(i.e. they should be a path on the local machine or a network path like
\\servername\repositories...).

Nope - first thing I checked - machine name has not changed.

The SLD import process makes a record of the component in the database so
you will have to reimport your custom SLD's if you go this route.

Interesting. The help files talk about backing up the component database
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/ht
ml/xetskbackingupcomponentdatabase.asp), but imply that it's as simple as
copying the files and repositories. But I don't see how to tell MSDE where
to look for the database.

It's definitely possible to install on a network server although for
performance reasons I would suggest against it. Here is a link to installing
on the network. Follow item number 9.
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp

To install MSDE and the Component Database:
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp
http://msdn.microsoft.com/library/d...help/html/xetutinstallingdevelopmenttools.asp

Again, If I backed up the database using the suggestions in the previous
link and then copied the backup to a new machine, how would I tell the
database MSDE engine/server where to look for the repositories?


Thanks,
Dean

 

[Brad Combs]

Hi Dean,

Of course! I'm not sure why I didn't think of that before. Here is a snippet
from a batch file I use daily to connect / disconnect one of the 5 different
XPe databases I have on my system....

set DBMDF=C:\XPe\SP1\MantisSQLDB_Data.mdf
set DBLDF=C:\XPe\SP1\MantisSQLDB_Log.ldf
osql -E -Q "sp_attach_db 'MantisSQLDB', '%DBMDF%', '%DBLDF%'"

Just change the path to reflect your mdf and ldf files to attach. There is
alot of documentation on MSDN about oSQL utility.

If you want the entire script send me an email.

HTH,
Brad

 

[DPM]

Brad,

I took your snippet below, changed the paths and ran it. A log of what I
got below; basically, it seems that osql did not like the request. Can you
see why? Is it the double-quotes around "Windows Embedded Data" in the
query? If true, how do I fix it? BTW, running the batch without the
double-quotes around "Windows Embedded Data" fails the same way.

Thanks,
Dean


C:\WINNT>attach

C:\WINNT>set DBMDF=E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf

C:\WINNT>set DBLDF=E:\"Windows Embedded Data"\MantisSQLDB_Log.ldf

C:\WINNT>C:\"Program Files\Microsoft SQL Server"\80\Tools\Binn\osql -E -Q
"sp_at
tach_db 'MantisSQLDB', 'E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf',
'E:\"W
indows Embedded Data"\MantisSQLDB_Log.ldf'"
usage: osql [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w columnwidth]
[-a packetsize] [-e echo input] [-I Enable Quoted
Identifiers]
[-L list servers] [-c cmdend] [-D ODBC DSN name]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-n remove numbering] [-m errorlevel]
[-r msgs to stderr] [-V severitylevel]
[-i inputfile] [-o outputfile]
[-p print statistics] [-b On error batch abort]
[-X[1] disable commands [and exit with warning]]
[-O use Old ISQL behavior disables the following]
<EOF> batch processing
Auto console width scaling
Wide messages
default errorlevel is -1 vs 1
[-? show syntax summary]

C:\WINNT>

 

[Brad Combs]

Hi Dean,

Try this....

osql -E -Q "sp_attach_db 'MantisSQLDB', 'E:\Windows Embedded
Data\MantisSQLDB_Data.mdf', 'E:\Windows Embedded Data\MantisSQLDB_log.ldf'"

HTH,
Brad

Brad,

I took your snippet below, changed the paths and ran it. A log of what I
got below; basically, it seems that osql did not like the request. Can
you
see why? Is it the double-quotes around "Windows Embedded Data" in the
query? If true, how do I fix it? BTW, running the batch without the
double-quotes around "Windows Embedded Data" fails the same way.

Thanks,
Dean


C:\WINNT>attach

C:\WINNT>set DBMDF=E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf

C:\WINNT>set DBLDF=E:\"Windows Embedded Data"\MantisSQLDB_Log.ldf

C:\WINNT>C:\"Program Files\Microsoft SQL Server"\80\Tools\Binn\osql -E -Q
"sp_at
tach_db 'MantisSQLDB', 'E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf',
'E:\"W
indows Embedded Data"\MantisSQLDB_Log.ldf'"
usage: osql [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w columnwidth]
[-a packetsize] [-e echo input] [-I Enable Quoted
Identifiers]
[-L list servers] [-c cmdend] [-D ODBC DSN name]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-n remove numbering] [-m errorlevel]
[-r msgs to stderr] [-V severitylevel]
[-i inputfile] [-o outputfile]
[-p print statistics] [-b On error batch abort]
[-X[1] disable commands [and exit with warning]]
[-O use Old ISQL behavior disables the following]
<EOF> batch processing
Auto console width scaling
Wide messages
default errorlevel is -1 vs 1
[-? show syntax summary]

C:\WINNT>

Hi Dean,

Of course! I'm not sure why I didn't think of that before. Here is a snippet
from a batch file I use daily to connect / disconnect one of the 5 different
XPe databases I have on my system....

set DBMDF=C:\XPe\SP1\MantisSQLDB_Data.mdf
set DBLDF=C:\XPe\SP1\MantisSQLDB_Log.ldf
osql -E -Q "sp_attach_db 'MantisSQLDB', '%DBMDF%', '%DBLDF%'"

Just change the path to reflect your mdf and ldf files to attach. There
is
alot of documentation on MSDN about oSQL utility.

If you want the entire script send me an email.

HTH,
Brad

 

[DPM]

Brad,

It appeared to execute without error (in fact in produced no output at all).
But CDM on a remote machine claims it cannot connect to the database.

Any advice or tools that I can use to debug what's going on?

Thanks for your help.

Regards,
Dean

Hi Dean,

Try this....

osql -E -Q "sp_attach_db 'MantisSQLDB', 'E:\Windows Embedded
Data\MantisSQLDB_Data.mdf', 'E:\Windows Embedded Data\MantisSQLDB_log.ldf'"

HTH,
Brad

Brad,

I took your snippet below, changed the paths and ran it. A log of what I
got below; basically, it seems that osql did not like the request. Can
you
see why? Is it the double-quotes around "Windows Embedded Data" in the
query? If true, how do I fix it? BTW, running the batch without the
double-quotes around "Windows Embedded Data" fails the same way.

Thanks,
Dean


C:\WINNT>attach

C:\WINNT>set DBMDF=E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf

C:\WINNT>set DBLDF=E:\"Windows Embedded Data"\MantisSQLDB_Log.ldf

C:\WINNT>C:\"Program Files\Microsoft SQL Server"\80\Tools\Binn\osql -E -Q
"sp_at
tach_db 'MantisSQLDB', 'E:\"Windows Embedded Data"\MantisSQLDB_Data.mdf',
'E:\"W
indows Embedded Data"\MantisSQLDB_Log.ldf'"
usage: osql [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w columnwidth]
[-a packetsize] [-e echo input] [-I Enable Quoted
Identifiers]
[-L list servers] [-c cmdend] [-D ODBC DSN name]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-n remove numbering] [-m errorlevel]
[-r msgs to stderr] [-V severitylevel]
[-i inputfile] [-o outputfile]
[-p print statistics] [-b On error batch abort]
[-X[1] disable commands [and exit with warning]]
[-O use Old ISQL behavior disables the following]
<EOF> batch processing
Auto console width scaling
Wide messages
default errorlevel is -1 vs 1
[-? show syntax summary]

C:\WINNT>

Hi Dean,

Of course! I'm not sure why I didn't think of that before. Here is a snippet
from a batch file I use daily to connect / disconnect one of the 5 different
XPe databases I have on my system....

set DBMDF=C:\XPe\SP1\MantisSQLDB_Data.mdf
set DBLDF=C:\XPe\SP1\MantisSQLDB_Log.ldf
osql -E -Q "sp_attach_db 'MantisSQLDB', '%DBMDF%', '%DBLDF%'"

Just change the path to reflect your mdf and ldf files to attach. There
is
alot of documentation on MSDN about oSQL utility.

If you want the entire script send me an email.

HTH,
Brad