cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

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

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!
|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create jobs
Getting Error:

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

Tried several different job types always same result?

Installing SP1 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create jobs
Getting Error:

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

Tried several different job types always same result?

Installing SP1 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

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

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

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

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?
Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>
|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>