I'm trying to get the NXT module to run a program that makes a tetrix motor run. But I have run into a few problems.
This is my current code:

#pragma config(Hubs, S1, HTMotor, none, none, none)
#pragma config(Sensor, S2, touch, sensorTouch)
#pragma config(Motor, mtr_S1_C1_1, motorD, tmotorNormal, openLoop)
#pragma config(Motor, mtr_S1_C1_2, motorE, tmotorNormal, openLoop)
//*!!Code automatically generated by 'ROBOTC' configuration wizard !!*//

task main()
{
motor[motorD] = 50;
motor[motorE] = 50;
wait1Msec(4000);

motor[motorD] = -50;
motor[motorE] = -50;
wait1Msec(4000);
}


And I have the current platform type is set to Nxt + tetrix/matrix, and have the motors hooked up, and the power is on.
Any idea why its not working?

The first thing I would look at is the connection of the components. According to your code, your tetrix motor controller should be connected to sensor port 1 (S1). Make sure the tetrix motor controller has power (a red LED light should be ON). The two motors should be connected to the "motor 1" and "motor 2" ports on the tetrix.

Yes, the wire is connected to Motor 1 and motor 2, going through sensor port 1. The red power light is on.
The motors are not moving.

Well, I found out, when I run the motor, I can feel it vibrating, but It doesn't move.
Has it burnt out?

I have no experience with TETRIX, but if it's vibrating I'd say that there are either stuck or broken gears.

What about setting power to 100 instead of 50. In any case, it does sound like there is a motor problem (or a motor controller problem). Do you have another motor or another motor controller to try with?

I tried changing power levels.
When I changed it to 100, it no longer vibrated.
But, I am meeting with my team in a few days, so we will have some other motors to work with.

I agree with MHTS and NeXT-Generation, if the motor is vibrating (but not moving) there may be an issue with the motor or the motor controller. I would double-check all of your connections (and make sure the battery is fully charged) and possibly wire up a different motor for testing. The only downside to that would be if the motor controller is bad it could theoretically damage the motor, but since DC motors do not have polarity (they can be run with either a positive or negative voltage range) you run less of a risk of burning them out simply by testing them.