Friday, March 30, 2012

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 to SQL2000

I would like to know if it's possible to transfer a database from MSDE to SQ
L 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000

MSDE to SQL2000

I would like to know if it's possible to transfer a database from MSDE to SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000

MSDE to SQL Server Express

Hi - I have an MSDE database running on my server - I'd like to port my asp.net 1.1 app to asp.net2, and make use of SQL 2005 Express.

How do I transfer my data from an MSDE database to SQL Server Express, keeping intact all of my unique ID fields, indexes, and SPs (I don't have any functions or views)

Thanks for any help,

Mark

Your best bet is either to "detach" it on the MSDE side, and "attach" it or "restore from backup" on the SQL 2005 side, or use DTS (data transformation services).

|||Hi - it's just SQL Server 2005 Express I have available, so no management tools are there to allow me to 'restore from backup' - I'm not sure it supports DTS either.

Has anyone else been able to do this?

Thanks, Mark|||

Even with SQL Express you should have the ability to detach the database. You need the Management studio installed to work with the Express server engine though. You can download it here.

http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en

|||You don't have to detach from SQL Express if you are using a file based database (You are if you use the AttachDB attribute in your connect string). Just stop whatever application that uses it, and copy the mdb/ldb files to SQL Sever 2005 and attach.

MSDE to SQL Server 2005 Express

Howdy,
My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?
I've searched MSDN but really can't find what I'm looking for.
Thanks,
David Lozzi
Web Applications Developer
dlozzi@.(remove-this)delphi-ts.comHello David,

> Outside of the
> connection string, will any syntax in my existing ASP.NET
> script/stored procs have to change to support SQL 2005?
Without specifics, its hard to say precisely. Some things change some, a
few a lot, most hardly at all. There's an upgrade advisor tool on the distri
bution
media and here [0] that I'd recommend starting with. It should catch a major
ity
of the changes needed with a minimum of effort.

> Is the
> migration process painless?
Again, that depends on what you've done in the past. I suspect not, but the
upgrade advisor will help you know more for sure.
[0]: http://www.microsoft.com/downloads/...&displaylang=en
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

MSDE to SQL Server 2000 connection drops on XP Pro

Using MSDE 2000 SP3
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql