Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Job Scheduling Window

Updated: 21 May 2010 | 5 comments
acurler's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello -

I installed the Deployment Console on two of our staff member's pc's. When they schedule a job the job scheduling window does not come up and the job does not get scheduled. If they schedule it through the web console it works fine.

We are using DS 6.9 SP2. I'm not so sure that it's really a 6.9 issue because when we had 6.8 I installed the console on my pc and the same thing was happening. I have the option of using the console from the server, they don't.

Thank you,
Ann

Group Ownership:

Comments

Biohazzard's picture
23
Apr
2009
1 Vote +1
Login to vote

I have the Deployment Console

I have the Deployment Console installed on a remote machine for our helpdesk (because they can't get to the server). When i upgraded from 6.9 to sp1 it broke and even though i reinstalled it , i couldn't get it working. i had to copy some of the .dll's from server over to the install directory of the remote console. that seemed to fix it for me.

acurler's picture
23
Apr
2009
1 Vote +1
Login to vote

Do you know what .dll's you

Do you know what .dll's you copied?

Biohazzard's picture
23
Apr
2009
1 Vote +1
Login to vote

From the Server I copied all

From the Server I copied all the .dll's from the Altris/Express/Deployment Server dir (excluding any non english files _de, _es, etc..) and copied them to the remote machine. This was so I knew the versions were the same. It seemed to work for me and the remote console worked fine.

acurler's picture
27
Apr
2009
1 Vote +1
Login to vote

Thank you. That worked.

Thank you. That worked.

Phyrant's picture
27
Apr
2009
1 Vote +1
Login to vote

RE: dll's

Considering that copying the dll's made it work for you it sounds like the users that the console wasn't working correctly before didn't have rights to access the dll's on the server. Just something to look into in case you have any other problems like this.