I ran that describe command from a cmd shell without problem.
Nothing obviously different from any other CL description. I redirected it to a file and saw nothing but ASCII. I had a job mapped to a different folder that also failed the same way, and it did not have CL 74865 in it change history. Problem overcome- Since I posted that problem, all of the jobs I recently changed to use the global password started to fail with the same message. (Of course, these were the most important...). I tried everything I could to fix it. I finally looked at the "advanced" P4 plugin options. One or more of these changes fixed the problem- - set a limit to 1000 for "Changelist file limit" - set "First change list to track" to be a number greater than the last real CL. Perhaps the root cause was an out of memory exception wrongly interpreted as a security issue? On Tuesday, August 28, 2012 5:03:54 PM UTC-7, Rob Petti wrote: > I have never seen that before. I'll take a look. It also seems like it > failed to get the change log description for 74865, which is why it's > attempting to log in again. Is there anything about that change that would > cause that command to output something non-standard? > >> >>> >> >>
