Ethernet Error

[Mark Wheaton]

Please see bottom of this thread Page 3 for new PT 8 info!!

I have this problem with my Ethernet connection to my D-Command.
I have the updated D-Command firmware as of Pro Tools HD 7.4cs7
I have OSX 10.4.11
When I have to force quit Pro Tools (usually due to a VI freeze)
And, I do not restart my computer and D-Command
I get this dialog after relaunching Pro Tools:
An Error occurred while trying to establish Ethernet commmunications. Please check all Ethernet connections.
I click OK, the same dialog comes up a second time and then I am in Pro Tools with the ethernet connection to the D-Command turned off. If I go to the Peripherals Dialog and attempt to reconnect, I get the same message.

I must at this point restart the computer and reboot the D-Command for the dialog to go away and have the connection to D-Command restored.

[DigiTechSupt]

Have you tried going to the Network control panel and toggling on/off the ethernet connection, or having it renew the DHCP lease by clicking on 'Advanced' and then on the 'Renew DHCP Lease' button?

[Mark Wheaton]

I will try this, but I have not been getting the freeze ups that cause this in the last week. Hopefully for unknown reasons, problem solved...HaHA

[Mark Wheaton]

More info on this error as it has shown up again.
I did have another crash out of Pro Tools due to a beta test I was doing and when I relaunch Pro Tools with out a restart of both the Computer and the D-Command I still get this error.

I have also had incidents in the last few days where I did a legal Quit of Pro Tools, did not restart and got the same error.

This error does not go away by restarting the Hub between my D-Command and my Computer. It does not go away by adjusting anything as described by Digi in the Network Control Panel. If I go through the two dialogs, Pro Tools completes it's launch with no D-Command.

When you go to the Peripherals and try to re-establish you get the same error.

the only workaround is a complete reboot of Pro Tools and the D-Command.

[DigiTechSupt]

Can you use the Tech Support Utility to post a list of installed plug-ins (you can find the TSU in the General Troubleshooting thread..)?

I suspect you may have an incompatible plug-in installed.

I would be curious if you tested this from a new Administrator account if you still have the problem - this would help identify if it's something about your current account causing the problem.

[Mark Wheaton]

I did the Version test and I have the text file, should I attach that to an email or just post in a reply?

[Mark Wheaton]

Hello Digi I posted the list of plug ins and have not heard back. By the way, the delete prefs voodoo does not solve the issue.

[Chris Lambrechts]

What happens with only the digirack plugins in there ?

You could move all plugins to the unused folder and just leave the mixer plugins in there if you want.

Make sure you trash your prefs (DAE / digisetup) when you do this.

Do you still get the error ?

if so then I would seriously start considering a clean install. I would even go for a COMPLETE clean install. starting with the OS.


Yes I know ... a hassle ... well ... try a new admin account first if you like. Keith already proposed to do that in a previous reply but in the end there's no 2 ways around it and often with these things ... instead of searching for 72 hours and still not finding what the exact cause is, you may as well at some point bite it and go for a clean / fresh install. It will save you time in the end.

Definitely try the digirack plugins only first. if that solves it you most likely have a plugin causing trouble.


Chris

[DigiTechSupt]

What, exactly, was the beta test you were doing originally?

I'm really not sure what's causing the problem. Have you tried a new admin account? If not - you should. That will help narrow down the problem.

Also, have you tried connecting the D-Command to the computer directly, to rule out a problem with the hub? You might just try resetting the hub as well.

A firmware reset of the D-Command may fix it, if it's corrupted somehow:

http://www.digidesign.com/index.cfm?...0&itemid=21606

Lastly, an uninstall/reinstall of Pro Tools may help - it could be a corrupted D-Command profile. Do a clean uninstall, restart and reinstall then test again.

[Mark Wheaton]

I will try the steps here, when I return next week. I would rather go through the whole clean install then do the process of elimination with plug ins, because I am a working studio and it takes time for this error to show up sometimes. I can't afford to run on reduced plug ins for days until I see a pattern, but I will approach the reinstall idea. Thanks