PT9 Error on Launch

[ffzeus]

2nd Gen iLok and PT9 on Win7 x64 system having the same issue. Was running fine for the last two months. Plugged another USB device into the adjacent port and can no longer launch PT9. Get "Error, missing iLok authorization for "Pro Tools 9". Please insert the necessary iLok to continue.

Have the latest drivers from the iLok site as well as the client helper software. It started after plugging another USB device into an adjoining port.

Machine is ASUS motherboard P6T7WS Supercomputer with i7 975 Extreme processor, 12GB matched triple channel DDR3 @ 1600Mhz, 3 x NVIDIA based XFX 280 GTX video in SLI, 1 KW PC Power and Cooling PSU, RAID 10.

Have the 3rd Gen Mbox attached by USB as well as a hub which runs a multifinction EPSON printer, Nostromo n52 and ioGear 321 Bluetooth radio. Logitech G19 is also connected by USB as is an APC Smart-UPS 2200.

But once again, ProTools launched and ran fine for the last two months. The problems began last night when I plugged my iPhone cable into the adjoining USB socket. The iLok site sees the iLok dongle and will complete an update. It even recognozes the PT9 license on their site.

Any further help would be appreciated. In the middle of recording some bass tracks for production and this doesn't help.

Z

Computer
Model : OEM System Product Name
Workgroup : Workgroup
Host Name : User
User : User

Processor
Model : Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz
Speed : 3.48GHz
Cores per Processor : 4 Unit(s)
Threads per Core : 2 Unit(s)
Type : Quad-Core
Integrated Data Cache : 4x 32kB, Synchronous, Write-Thru, 8-way, 64 byte line size, 2 threads sharing
L2 Cache : 4x 256kB, ECC, Synchronous, ATC, 8-way, 64 byte line size, 2 threads sharing
L3 Cache : 8MB, ECC, Synchronous, ATC, 16-way, Exclusive, 64 byte line size, 16 threads sharing

Computer
Mainboard : ASUS P6T7 WS SUPERCOMPUTER
BIOS : AMI (OEM) 0904 09/24/2010
Bus(es) : ISA X-Bus PCI PCIe IMB USB FireWire/1394 i2c/SMBus
Multi-Processor (MP) Support : No
Multi-Processor Advanced PIC (APIC) : Yes
Total Memory : 12GB DIMM DDR3

Chipset
Model : ASUS X58 I/O Hub
Front Side Bus Speed : 2x 3.22GHz (6.43GHz)

Chipset
Model : Intel Core Desktop (Bloomfield) UnCore
Front Side Bus Speed : 2x 3.22GHz (6.43GHz)
Total Memory : 12GB DIMM DDR3
Channels : 3
Memory Bus Speed : 2x 804MHz (1.6GHz)

Memory Module(s)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)
Memory Module : G.Skill F3-16000CL9-2GBTD 2GB DIMM DDR3 PC3-16000U DDR3-2000 (9-9-9-24 4-33-10-5)

Video System
Video Adapter : 3x NVIDIA GeForce GTX 280 (240 SM4.0 1.46GHz, 1GB DDR3 2.49GHz 512-bit, PCIe 2.00 x16)
Video Adapter : 3x NVIDIA GeForce GTX 280 (240 SM4.0 1.46GHz, 1GB DDR3 2.49GHz 512-bit, PCIe 2.00 x16)

Graphics Processor
OpenCL Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
OpenCL Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
OpenCL Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
Compute Shader Processor : 3x NVIDIA GeForce GTX 280 (240SP 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
CUDA Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
CUDA Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)
CUDA Processor : NVIDIA GeForce GTX 280 (240SP 30C 1.46GHz, 1GB DDR3 2.49GHz 512-bit)

Storage Devices
4x Seagate ST3500630NS (1TB, RAID10/SATA300, 3.5", 16MB Cache) : 932GB (C:)
HL-DT-ST BDDVDRW UH08LS10 (SATA150, BD-R, DVD+-RW, CD-RW, 4MB Cache) : 327MB (D:)

Logical Storage Devices
System Reserved : 100MB (NTFS)
Hard Disk (C:) : 931GB (NTFS) @ 4x Seagate ST3500630NS (1TB, RAID10/SATA300, 3.5", 16MB Cache)
Audio CD (D:) : 0bytes (CDFS) @ HL-DT-ST BDDVDRW UH08LS10 (SATA150, BD-R, DVD+-RW, CD-RW, 4MB Cache)

Peripherals
LPC Hub Controller 1 : ASUS LPC Interface Controller
LPC Legacy Controller 1 : T0 A5-13
Audio Device : ASUS HD Audio Controller
Audio Codec : Analog Devices 989Bh
Disk Controller : ASUS ICH8R (ICH8) SATA RAID Controller
USB Controller 1 : ASUS USB UHCI Controller #4
USB Controller 2 : ASUS USB UHCI Controller #5
USB Controller 3 : ASUS USB UHCI Controller #6
USB Controller 4 : ASUS USB EHCI Controller #2
USB Controller 5 : ASUS USB UHCI Controller #1
USB Controller 6 : ASUS USB UHCI Controller #2
USB Controller 7 : ASUS USB UHCI Controller #3
USB Controller 8 : ASUS USB EHCI Controller #1
FireWire/1394 Controller 1 : ASUS VT6315 Series Firewire Controller
SMBus/i2c Controller 1 : Intel ICH SMBus

Printers and Faxes
Printer : Send To Microsoft OneNote 2010 Driver (1200x1200, Colour)
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : EPSON Artisan 810 Series (360x360, Colour)
Fax : EPSON PC-FAX driver (203x203)
Printer : EPSON Artisan 810 Series (360x360, Colour)

Network Services
Network Adapter : Bluetooth Device (Personal Area Network) (Ethernet)
Network Adapter : TeamViewer VPN Adapter (Ethernet)
Network Adapter : Realtek Virtual Miniport Driver for Teaming (NDIS 6.2) #2 (Ethernet, 2Gbps)

Power Management
Mains (AC) Line Status : On-Line
Battery No 1 : 100%

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7601 (Service Pack 1)
Platform Compliance : x64

Windows Experience Index
Current System : 6.0

[ffzeus]

So, after trying all of the things in the multiple posts on these forums, multiple times, one of them suddenly started working for no explainable or reproduceable reason.

If I reboot the machine and then Eject the iLok through the Win 7 interface, then physically remove it, start PT9 as Admin user, when the prompt pops up, reinsert the iLok, and then click yes on the prompt, it will continue to rn as long as the machine is not rebooted. As soon as the machine is rebooted, the process has to be repeated.

I had tried this several times without succes and then it just started working. I am just waiting now for the other shoe to drop and have it stop working as randomly as it started.

Z

[albee1952]

Just an opinion here, but I wonder if maybe you are trying to do too many things with this computer. Most of us that have solid PT systems are using the computer for nothing but recording. That allows you to tweak the system for ideal recording, without compromises. First thing I see is RAID, which is not supported or recommended for Pro Tools. Your system is only seeing a C: drive and Pro Tools sessions need to be on a separate physical drive. I would start over with no RAID, 1 drive for C:, 1 drive for samples and 2 drives for recording(copy sessions so they exist on both drives as a simple backup strategy). Then I would use Acronis True Image to save drive images(or straight clone) to a USB drive. Next thing is 3 video cards in SLI, when 1 card is plenty for Pro Tools(PT graphics requirements are very modest). If the Mbox works when plugged straight in, that is the preferred setup(instead of using a hub). Bluetooth and networking should be disabled when running Pro Tools. Your machine should be a monster, but it won't be until you set it up correctly. If you need this rig to do other tasks, then I would install a 3-4 slot SATA drive cage and have separate drives for recording, and other tasks(so you don't need to compromise things as much). Just one user's opinion

[ffzeus]

I understand your view and don't disagree. I am not a sound engineer or studio tech or etc. I am a session bass player that records tracks for a couple of local artists to put on their self produced CD's. I don't get compensated for my efforts and don't expect any as both of these folks are good friends.

All of this adds up to say I built this machine as stout as possible to handle the multiple tasks it would need to accomplish as I don't have the resources to afford multiple boxes.

But, putting that aside, this issue affects folks that have dedicated boxes as well, so I doubt it is related to the multiple use.

In the end, I do agree with your sentiment though.

Z

After thinking about this further...after spending 40+ years as a computer and network engineer, and knowing that some of the best file system performance is achieved through RAID arrays, to read that PT does not play well with them is shocking to say the least. I wish I had come across this tidbit prior to purchasing this. I would have given it a second thought. Redundant Arrays of Inexpensive Disks have been arround since way before the 8088 days (were talking the 70's). To think a company would write a piece of software and publish it knowingly as a product that will not perform welll under what many today consider the "standard" for hard drives is unscionable. I personally spec all my boxes that have any meaning with a minimum RAID 10 if not RAID 50 or 60. I find that this box, even multi-purposed as it is, allows me to playback and record off the single RAID array without issue, when PT is authorizing. Maybe the software folks at AVID don't have a good hardware reference for building upon, ormaybe they are only interested in publishing mediocre software. I don't know. I do know that all of the systems I administer, including multiple systems that stream AV data, all use RAID arrays and have no problem with them. YIKES!

[ffzeus]

http://www.youtube.com/watch?v=f4zyjLyBp64 anyone?

[jntracks]

i would be careful letting your expertise in computer systems convince you that you know something about pro tools audio engine that you don't.
i didn't code pro tools ether but, it does need to take control of all the storage related to the session that's open. it's logical to assume it can't get enough control while seeing through a RAID controller. also RAID arrays are inherently less reliable, in the pro audio world, performance is prioritized only when it doesn't impact reliability.
we all don't work for avid but that's my thoughts about pro tools and RAID. FWIW. since you seemed to want a comment.

as for your USB problem. you said it happened after you used a device that was new to the computer in the adjacent port. perhaps the device in question installed a driver or otherwise software that is causing the change in behavior of the USB controller.
first i would check for updates in the PACE iLok software. if you are already up to date, clean them out and re-install them. if that doesn't fix your problem, have you considered using a system restore point from before the date you used this other USB device? maybe do system restore first. whichever you think is easier.

[aboriginal]

FFzeus,

It would be interesting to know what driver was installed after connecting your IPhone.

Some of us are also experiencing this issue as well but only after using the new ilok2. This issue does not occur with an Ilok 1st generation.

Question, do you have your network adaptor disabled or enabled?

I noticed that I only got this error when my network adaptor was disabled when using an ilok2. As soon as I enable the NIC card, PT launched with no errors. Very strange! DTS was made aware of this prior to the 9.03 update and I believe he/she is looking into it. I haven't re-tested this yet as I'm still using my ilok1, but I doubt this was addressed with 9.03.

It is very interesting that you were fine prior to connecting your IPhone though. I don't use an IPhone, but I have connected my Blackberry Bold to my desktop. As jntracks hinted, perhaps its the driver which is used to read on-board device memory causing this issue? Ilok2 driver conflict??

Here's the link regarding this issue..

http://duc.avid.com/showthread.php?p...15#post1792815


ABS

[ffzeus]

Hi,

I have my network adapters teamed and enabled. The iPhone had already been attached to this machine before, just not through this particular USB port.

Thanks for thre reply. I had read that post also. I can tell you the version of 9.03 that is currently up does not address the issue as that is something I tried as a solution.

Keep hoping Digi will comment on this rather than say nothing and just ask for info. Most of the threads I have read, it seems like they don't feel it is much of an issue.

Thanks again for the reply. I am on the track that the other thread was in that a driver Avid uses conflicts with others for USB connected equipment. I haven't run across any threads from folks stating they have the issue with Firewire.

Hopefully their engineers will root it out and a fix will come in a future release.

Z