Bad Behavior has blocked 1706 access attempts in the last 7 days.
Powered by LifeType
Test Director uses the IIS IUSR_SERVERNAME user by default, and if you haven't set your permissions correctly on your directories, this user will not have access to the files.
To see if this is the problem or not, go to the IIS Manager and the TDBIN directory, then choose directory security (make sure it is on anonymous access only) and edit the anonymous user to be the local Administrator account (type in the password).
Then try accessing your server again. If this works, then you know it is a permissions issue, and you should probably go change the anonymous user back to the IUSR_XXXX account, and fix the directory/NTFS permissions to allow the IUSR_XXX user access to the necessary Test Director directories.
For the record/search engines:
The error I got when I had this problem was:
Error in parameter: [TDsrvURL]
Error: Server is not initialized
Press OK to continue or CANCEL to close application
Not the most intuitive error message in the world
Serena would want me to tell you to check out their Build product, which my company has looked at a little, but we haven't yet started using it.
Before you spend tons of money, see my post about Serena's products.
To set up TestDirector as a service:
1. In the Start menu, choose Run. The Run dialog box opens.
2. In the Open box, type DCOMCNFG. The Distributed COM Configuration Properties dialog box opens.
3. Under Applications, select Mercury TD2000 Server and click the Properties button.
4. Click the Identity tab.
5. Select This user and type a local NT username and password of the user that is to be used to run as a service. Make sure to specify the username with the domain name, for example, DOMAINmyuser. Administration privilege required for this user.
6. Click the Security tab.
7. Select Use custom access permissions and click the Edit button. The Registry Value Permissions dialog box opens.
8. Click the Add button. The Add Users and Groups dialog box opens.
9. Click the Show Users button.
10. Choose the user you added in step 5, and click the Add button. Make sure you set the Type of Access to 'Allow Access'.
11. In the Security tab, repeat steps 7-10 for the Use custom launch permission option.
Note: This time make sure you set Type of Access for the user to 'Allow Launch'.
12. Repeat steps 5-11 for the following applications: OTAScripting.CMailAll and OTAScripting. CCopyPaste.
Note: Either one or both of thee applications may appear in the Applications list. In the Identity tab, keep the default selection The launching user.
I also had a reboot the machine after making these changes.
For the directory permissions, you just need to set them as you would any directory, giving read and write to the IIS user. You should be able to search the internet for explicit instructions on how to set permissions appropriately, so it probably isn't worth my time to write those instructions.
Did you try my instructions at the top for making the web server run as the administrator?
What we now use is the PCLI language to get the files out of PVCS, and then a custom-built Perl script to run Microsoft's command line.
As a side-note, another perl script can be used interactively inside of Epsilon, for those of you who care about such things.
Do you currently have TD running as a service or not?
What user does it run under?