couldn't see some of the database in the object explorer window of Management Studio

hey guys,
I have one question. But it is not related with the Reporting Service. I got my computer set up with SQL Server 2005 version yesterday. When I connect to the database engine, I can see only system databases(master,model,msdb and tempdb) under the system database folder. I couldn't see other databases(like pubs,northwind) in the object explorer window of Management Studio. Do you have any idea how to solve this difficulty?

Thanks.

Amde

Hi,

no problem there. These databases aren′t installed by default. There are scripts to build up the database from scratch:

http://www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46A0-8DA2-EEBC53A68034&displaylang=en

Or you use the Adventureworks sample database:

http://www.microsoft.com/downloads/details.aspx?FamilyID=e719ecf7-9f46-4312-af89-6ad8702e4e6e&DisplayLang=en

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks a lot. I will work on that.

Amde

couldn't rename or delete maintenance plan in Management Studio

Hi,
I tried to rename and delete one old maintenance plan which is created by
other DBA and before the machine was renamed. But, I kept getting the
following error. I can rename and delete the maintenance plan I created.
An error has occurred while establishing a connection to the server. When
connecting to SQL server 2005, this failure may be cuased by the fact that
under the default settinfs SQL server does not allow remote connections
(provider: Named Pipes providers, error: 40 - could not open a connection to
SQL server) (Microsoft SQL server, Error: 53)
Shared Memory, TCP and Named Piples are all enabled.
Please advise.
Best Regards,
Lynn
I think the problem is that the maintenance plan use the Local Server
Connection which still point to the old machine name. (I couldn't move this
connection or modify the server name for this connection at all). I add
another connection, but I still couldn't delete this maintenance plan.
Please advise.
Best Regards,
Lynn
"Lynn" wrote:

> Hi,
> I tried to rename and delete one old maintenance plan which is created by
> other DBA and before the machine was renamed. But, I kept getting the
> following error. I can rename and delete the maintenance plan I created.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL server 2005, this failure may be cuased by the fact that
> under the default settinfs SQL server does not allow remote connections
> (provider: Named Pipes providers, error: 40 - could not open a connection to
> SQL server) (Microsoft SQL server, Error: 53)
> Shared Memory, TCP and Named Piples are all enabled.
> Please advise.
> --
> Best Regards,
> Lynn
|||I've been pounding my head with a similar problem. A Server was renamed and
now I can't do anything with the plan.
Any more thoughts?
"Lynn" wrote:
[vbcol=seagreen]
> I think the problem is that the maintenance plan use the Local Server
> Connection which still point to the old machine name. (I couldn't move this
> connection or modify the server name for this connection at all). I add
> another connection, but I still couldn't delete this maintenance plan.
> Please advise.
> --
> Best Regards,
> Lynn
>
> "Lynn" wrote:

Could not find server

I have linked a server withinh the "SQL Server Management Studio
Express"
I also created a database where I created a view using the openquiery
statement.
The view runs perfectly within the "SQL Server Management Studio
Express"
I created a new project with "Microsoft Visual Studio 2005"
I created a shared data source to the database where I created the
views.
The data source is OK because I can see the cretaed views on the Query
Builder.
Once I created the query on the Query Builder and I try to run it, the
following message appears:
"SQL Execution Error
Error Source: .NetSqlClient Data Provider
Error Message: Could not find server 'xxx' in sysservers. Execute
sp_addlinkedserver to add the server to sysservers.
Could not use view or function 'xxx' because of binding errors"
I have looked for server 'xxx' in sysservers and it is there, so I do
not understand where the error originates.
Any help would be most appreciated.
Abraham Hirsch
Mexico CityAbraham,
Is the working connection local and the non-working connection remote?
If so, open SQL Server Configuration Manager and adjust connection
protocols for SQL Express.
Andrew Watt MVP
On 9 Jun 2006 11:25:03 -0700, "Eibi" <ahirschp@.gmail.com> wrote:
>I have linked a server withinh the "SQL Server Management Studio
>Express"
>I also created a database where I created a view using the openquiery
>statement.
>The view runs perfectly within the "SQL Server Management Studio
>Express"
>I created a new project with "Microsoft Visual Studio 2005"
>I created a shared data source to the database where I created the
>views.
>The data source is OK because I can see the cretaed views on the Query
>Builder.
>Once I created the query on the Query Builder and I try to run it, the
>following message appears:
>"SQL Execution Error
>Error Source: .NetSqlClient Data Provider
>Error Message: Could not find server 'xxx' in sysservers. Execute
>sp_addlinkedserver to add the server to sysservers.
>Could not use view or function 'xxx' because of binding errors"
>I have looked for server 'xxx' in sysservers and it is there, so I do
>not understand where the error originates.
>Any help would be most appreciated.
>Abraham Hirsch
>Mexico City|||Both connections are local!
Andrew Watt [MVP] wrote:
> Abraham,
> Is the working connection local and the non-working connection remote?
> If so, open SQL Server Configuration Manager and adjust connection
> protocols for SQL Express.
> Andrew Watt MVP
> On 9 Jun 2006 11:25:03 -0700, "Eibi" <ahirschp@.gmail.com> wrote:
> >I have linked a server withinh the "SQL Server Management Studio
> >Express"
> >I also created a database where I created a view using the openquiery
> >statement.
> >
> >The view runs perfectly within the "SQL Server Management Studio
> >Express"
> >
> >I created a new project with "Microsoft Visual Studio 2005"
> >I created a shared data source to the database where I created the
> >views.
> >
> >The data source is OK because I can see the cretaed views on the Query
> >Builder.
> >
> >Once I created the query on the Query Builder and I try to run it, the
> >following message appears:
> >"SQL Execution Error
> >Error Source: .NetSqlClient Data Provider
> >Error Message: Could not find server 'xxx' in sysservers. Execute
> >sp_addlinkedserver to add the server to sysservers.
> >Could not use view or function 'xxx' because of binding errors"
> >
> >I have looked for server 'xxx' in sysservers and it is there, so I do
> >not understand where the error originates.
> >
> >Any help would be most appreciated.
> >
> >Abraham Hirsch
> >Mexico City

could not find row in sysindexes for database

I am trying to attach a database that was created on another server. I believe the database was created using SQL Server Management Studio Express 2005. Now, I have successfully attached the database in my development environment, which is using SQL Server Management Studio Express 2005.

However, when I tried to attach the database onto our production server, which is SQL Server 2000 I received the error:

Error 602:
Could not find row in sysindexes for database ID 18, object ID 1, index ID 1. Run DBCC CheckTable on sysindexes.

In my development environment, I ran DBCC CheckDB on the source database and no errors are returned.

I aslo checked the compatibility level under the database properties and it shows: Sql Server 2000 (80)

So, this should not be a version incompatibility issue. What is causing the attach to fail on SQL Server 2000?

Thanks for any help.

What I know is:

If you have an .mdf file in SQL Server 2000, then you attached it to SQL Server 2005 ... no way you can use it (the .mdf file) again with SQL Server 2000.

What I think about is SQL Serve 2006 .mdf files can not be used with SQL Server 2000!!

Try Backup/Restore option or Copy Database Wizard.

Good luck.

|||

Are you trying to attach a SQL 2005 database to a SQL 2000 server? If so, that's the issue. Obviously you can upgrade (2000 --> 2005), but you can't downgrade.

-Damien

|||

CS4Ever:

What I know is:

If you have an .mdf file in SQL Server 2000, then you attached it to SQL Server 2005 ... no way you can use it (the .mdf file) again with SQL Server 2000.

What I think about is SQL Serve 2006 .mdf files can not be used with SQL Server 2000!!

Try Backup/Restore option or Copy Database Wizard.

Good luck.

Here is a link that support what I wrote and it marked as answered in MSDN forum: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=165696&SiteID=17

This link might be helpful for you as well: http://sqlserver-qa.net/blogs/tools/archive/2007/08/14/error-could-not-find-row-in-sysindexes-for-database-8966-823-and-602.aspx

Good luck.

Could not find file 'C:\WINDOWS\TEMP\

When I try to connect to the reporting server using sql server management studio, I get the following error

TITLE: Connect to Server

Cannot connect to hq-v-w2k3-rpt0.

ADDITIONAL INFORMATION:

System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.IO.FileNotFoundException: Could not find file 'C:\WINDOWS\TEMP\7cxlkihr.dll'.
File name: 'C:\WINDOWS\TEMP\7cxlkihr.dll'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, CompilerParameters parameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, CompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Evidence evidence)
at System.Web.Services.Protocols.SoapServerType..ctor(Type type, WebServiceProtocols protocolsSupported)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
End of inner exception stack trace (Microsoft.SqlServer.Management.UI.RSClient)

It was working until today. nothing changed except I got a microsoft update, could that have caused it?

Nevermind. There must have been something going on in my environment becuase I got another update Update for SQL Server 2005 (KB 932557) and now its fixed.

|||

Hi,

Could you please five the complete url where we can get the this update please. Thanks in advance for you help.

Thanks & Regards,

Venkat.

Could not find file 'C:\WINDOWS\TEMP\

When I try to connect to the reporting server using sql server management studio, I get the following error

TITLE: Connect to Server

Cannot connect to hq-v-w2k3-rpt0.

ADDITIONAL INFORMATION:

System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.IO.FileNotFoundException: Could not find file 'C:\WINDOWS\TEMP\7cxlkihr.dll'.
File name: 'C:\WINDOWS\TEMP\7cxlkihr.dll'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, CompilerParameters parameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, CompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Evidence evidence)
at System.Web.Services.Protocols.SoapServerType..ctor(Type type, WebServiceProtocols protocolsSupported)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
End of inner exception stack trace (Microsoft.SqlServer.Management.UI.RSClient)

It was working until today. nothing changed except I got a microsoft update, could that have caused it?

Nevermind. There must have been something going on in my environment becuase I got another update Update for SQL Server 2005 (KB 932557) and now its fixed.

|||

Hi,

Could you please five the complete url where we can get the this update please. Thanks in advance for you help.

Thanks & Regards,

Venkat.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

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

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create an user to SQL Server 2005

Hi,

I am trying to add "Remote Desktop Users" as a login group to SQL Server 2005 (i.e. so they can log into management studio). I get a "Not Found Error" (see below). But it is of course found, because I selected it :-) What is going on here? I see the "Administrators" group and various SQL Server groupls added automatically there, so there must be a way, right?

I know I can add each user in the group individually, but that seems overkill when I can just use the group in which they are contained.

Here is the error I get:

TITLE: Microsoft SQL Server Management Studio

Create failed for Login 'TESTSERVER\Remote Desktop Users'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Windows NT user or group 'TESTSERVER\Remote Desktop Users' not found. Check the name again. (Microsoft SQL Server, Error: 15401)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476

BUTTONS:

OK

This appears to be a defect within Management Studio: it qualifies the group using the machine name instead of "Builtin". I suggest that you open a bug at http://lab.msdn.microsoft.com/productfeedback/Default.aspx and put in it the information from this thread. Let me know if you need any help with filing the bug or if you wish that I would file it instead.

In the meantime, you can create such login by executing:

create login [Builtin\Remote Desktop Users] from windows;

Thanks
Laurentiu

|||Thank you Laurentiu. The script worked. I have indeed submitted a bug.|||Please note that I am the furthest thing from an expert that one can imagine, but...

I had a similar problem, but found an easy way to solve it.

Expand Security, right click Logins and select New Login
Click Search to the right of the Login Name box
Click the button Object Types
Select the box next to Groups|||

Hi ,

I am trying to create a new user in SQL Server 2005 with windows authentication.

This is the query i am trying to run.

create login [Builtin\User1] from windows

But i am getting error like "Windows NT user or group 'Builtin\waveset1' not found. Check the name again."

And the sql server is running on SQL and windows authuntication mode.

So anybody can help me what is the wrong.

I appreciate your response.

Thanks!