New SQL Express

I am working with Microsoft Office Access 2003 on MSWXP Professional SP2. In attempting to open one of the sample database projects that come with Access 2003, NorthwindCS.adp, I get the following message: "Microsoft Access could not find either Microsoft SQL Server 2000 Desktop Engine or Microsoft SQL Server installed on your computer. Click OK to display the Data Link Properties dialog box and log on to a remote server. If you want to install SQL Server 2000 Desktop Engine on this computer first, click Cancel, install it from the MSDE2000 folder on the Office CD-ROM, and then reopen this Access project". Instead of downloading & installing the Microsoft SQL Server 2000 Desktop Engine, I downloaded & installed the SQL Server 2005 Express Edition SP1 instead. After having restarted the computer and relaunching Access 2003 & opening the NorthwindCS.adp I still get the same message as mentioned previously above. My question is can the SQL Server 2005 Express Edition SP1 be used or must the SQL Server 2000 Desktop Engine be used instead. I understand that running Microsoft Windows Vista must use the SQL Server 2005 Express Edition SP1 but I am running MSWXP Professional SP2 instead. Advise?

Hi,

AFAIC remember 2003 ADP projects are not fully supported / working in conjunction with SQL Server Express even with t the compt. settings changed.

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de

new MSDE install fails with "instance name specified is invalid"

I am trying to put SQL Server 2000 and MSDE on same local machine. I install
ed 2000 Developer (from VS Tools for Office)using "typical" install level, u
sing the LocalSystem Account, so no password required. When I run C:\sql2ksp
3\MSDE\setup.exe (generated
by Office 2003 disk), the first thing that happens is dialog box that says "
instance name specified is invalid" and the setup is cancelled. When I tried
to do the MSDE install before the 2000, I got a "Strong SA password is requ
ired - use SAPWD switch to
supply the same", so I installed the 2000 and then came back to try MSDE, if
only because I couldn't figure out how to get Online Books going to find ou
t about how to supply SAPWD. There is no other instance of 2000, and none of
MSDE, on the machine. I t
hought the 2000 instance was unnamed. (?)
I am an almost complete rookie about SQL Server. Any help on instance name w
ould be appreciated, or the SAPWD which may be waiting for me. Thanks !hi Bob,
"Bob P." <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:111B62D3-B753-4A78-88BD-7309173DFE4F@.microsoft.com...
> I am trying to put SQL Server 2000 and MSDE on same local machine. I
installed 2000
> Developer (from VS Tools for Office)using "typical" install level, using
the LocalSystem
>Account, so no password required. When I run C:\sql2ksp3\MSDE\setup.exe
(generated by
>Office 2003 disk), the first thing that happens is dialog box that says
"instance name
>specified is invalid" and the setup is cancelled. When I tried to do the
MSDE install before
>the 2000, I got a "Strong SA password is required - use SAPWD switch to
supply the
>same", so I installed the 2000 and then came back to try MSDE, if only
because I couldn't
>figure out how to get Online Books going to find out about how to supply
SAPWD. There is
>no other instance of 2000, and none of MSDE, on the machine. I thought the
2000 instance
>was unnamed. (?)
> I am an almost complete rookie about SQL Server. Any help on instance name
would be
> appreciated, or the SAPWD which may be waiting for me. Thanks !
the first SQL Server instance you installed hase become the default instance
becouse you did not provide instance name...
in order to install other SQL Server and/or MSDE instancese, they must be
"named" instances...
please see
http://msdn.microsoft.com/library/d...
4xl.asp
for further info about all parameters accepted by the setup.exe installer
bootstrap of MSDE...
you can download Books On Line for free from
http://www.microsoft.com/sql/techin.../2000/books.asp
hth
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||See the sp3 readme for the valid options for setup.
814130 INF: How to Secure Network Connectivity for SQL Server 2000 Local
http://support.microsoft.com/?id=814130
829925 Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
http://support.microsoft.com/?id=829925
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

New Job Sql Server Agent error *FIXED*

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.|||I have SQL SERVER 2005 (SP2). I'm having the same problem. I upgraded the server via command prompt (c:/>setup SKUUPGRADE = 1). Still I'm having the same problem. Can any one tell me how to resolve this problem.

New Job Sql Server Agent error

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.

New Job Sql Server Agent error

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.