Job creation/run problem

Hello,

We have the same problem here. It is impossible to create/start a job (at step) from the job interface in our server.
It is possible to create the job via a client, then go to the server and update it. To start de job (at step) we have to start the job activity monitor. Then from there is it possible to start the job at a defined step...

This is very annoying...

Server config : Sqlserver 64 bit

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

Client config: Sqlserver 32 bit

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

The tech team said that sp2 is installed on the server...

Greetings

Hello,

I found a solution to my problem (not the resolution but though...)

So first of all, the 64 bit server solution is a mix of 64 bit and 32 bit applications. So the client on the 64 bit server has to be patched with the 32 bit version.... After that i was able to create jobs on the server. No confusion possible with the version, wrong patch is impossible...

The problem with the ssis, is that some part of it (excel connector for example) are only 32 bit and that the job is trying to use the 64 bit version of the dtsexec application.

In order to get rid of this you have to use the dtsrunui utility to make a command line. Then, you have to find the place of the 32 bit dtsexec app and then make a cmd task in your job when you launch the 32 bit version with the command line created with the ui... Then it is working...

Some words about patching etc... Dear collegues of microsoft, it would be nice to mention in the patch pages severals things...

- First give the link to all the patches in the same page instead of puting it in different pages. If we don't pay attention, we don't see that there are several critical update to the sp2.... And sorry but these patches needs to be applied (had too much problem with ssis, connectors,...)

- Second, mention that the 64 bit version patch has to be followed by the 32 bit for the client tools on the server (no mention in your sites...)

- Don't forget to put some warning into your commercial pages about the so bright 64 bit version... Yes it is true that this version is amazing and runing very fast, but the surrounding things are not totally developped (drivers, ssis, connectors, linked server,...). A server is not a standalone piece of work, it does communicate with other and when you have problem to do it, you have problem with the server and also into the trust to the product... Sqlserver 2005 is a so nice product that it's very disappointing to see these kinds of problems... !