When I hit play the now marker moves for about a second then stops. The project continues to plays as normal but with ZERO visual feedback as to where it is in the song. Same goes for the time clock. Hit play and it move forward by a second or so and stops. Song continues to play. _____I can click in the ruler area and move it like normal (that functionality hasn't changed)
This same thing also happens when recording. The now marker and clock don't move. When STOP is pressed the wave form that I just recorded then appears. Please note that the wave form isn't created in real time. This was not always the case obviously, it just happened and it happened when I started using a new sound card.
 
I'm not sure if the sound card has anything to do with it but I just installed a Digi 002 light piped to a ADA 8. All functionality is working fine except for the visual feedback of where I am in the song at any given point. Which is important to me while mixing, as it aids in automation greatly. Thanks for reading.
-----Things I have tried____------- 1. The pause/break keyboard button 2. Scroll Lock 3. Track view> OPTIONS now marker settings. 4. EDIT>preferences (every possible option) 5. Buffer sizes from 64 to 2024 6. New projects / old projects
----------------------------------------------------------------------------------------------------------------------------------
Windows 7 64 bit / Sonar X3 d studio / Intel core2 duo 2.4 quadcore / 8 gigs DDR3 / 1 gig graphix card / Digidesign 002 / ADA 8 digital pre amp

Sounds like you might have pressed the Pause key on your QWERTY keyboard accidentally.

Thanks Bristol_Jonesey but I did try that. LOL it's the first thing I listed in things I have tried:)
Do you or anyone think it could be a clock issue with the 002 and adat? The only reason I wouldn't think so is there is no Jitter/stutter during playback or recording.

This does sound like a clocking issue to me, but it is odd that that the audio playback is normal. I use ADAT input on the MOTU for output from an Alesis QSR, and slave the MOTU to the Alesis clock because the QSR isn't happy the other way around. I will get something like the behavior you describe if I forget to power up the QSR. The Now time will move intermittently as if SONAR's CPU Conservation Mode (Pause) is enabled. But I don't get any audio output at all when this happens.
 
Still, I would check all your sample rate settings, and make sure that the master/slave relationship between the ADA and the DIGI is correct, or maybe try swapping their roles.

Brundlefly thank you for the advice. A friend of mine also gave me the same advice. I will surely be working on it tonight. I'll update my findings tomorrow. Thank you for your thoughts!

Good day everyone. So I wasn't able to get it working with the digi 002. I tried disconnecting the ADA pre so there would be no slave/master issues. That didn't help. I tried making each the master and that didn't work. I tried updating drivers, that didn't work. When I plugged up every other sound card that I have (komplete audio 6, firewire 410 and fast track ultra) the issue was fixed. So it does seem to be a problem with the Digi 002. Has anybody else had this issue with any sound card? I know I can use any of my other interfaces but the digi is the best set up for external gear for mixing and recording more than 8 inputs at once. (Although its not very often I need to)

juicebass
Good day everyone. So I wasn't able to get it working with the digi 002. I tried disconnecting the ADA pre so there would be no slave/master issues. That didn't help. I tried making each the master and that didn't work. I tried updating drivers, that didn't work. When I plugged up every other sound card that I have (komplete audio 6, firewire 410 and fast track ultra) the issue was fixed. So it does seem to be a problem with the Digi 002. Has anybody else had this issue with any sound card? I know I can use any of my other interfaces but the digi is the best set up for external gear for mixing and recording more than 8 inputs at once. (Although its not very often I need to)

In general Digi hardware always produces these kinds of issues within SONAR. I've had numerous calls about this hardware showing these kinds of problems when I was working phones for Cakewalk. 
-DG

Dan was there ever a work around found? Or is it just what it is?

Since the problem is in Avid's court it's hard to do anything about it. I personally haven't found a workaround for the issue except for getting some new shiny gear.
-DG

hahahah thanks for the very helpful insight Dan. As much as I appreciate that I may have to live with this. The benefits in my case out weigh the issue. The digi accesses the rack gear so much easier than any of my other interfaces. When doing full fader mixing and effects it's fine. I can just switch to another interface for doing automation and fine tuning. Then back to the rack for mastering.
That being said. If anyone else has insight into this particular issue. I'm still open for suggestions. Thanks.