We're seeing a problem with the Profiler SP4 client. This problem  did
not occur in the SP4 beta. We have trace tables stored in the database
and can no longer open them up from Profiler using the File - Open -
Trace Table option or using the command-line parameters (which is how we
normally would do it).

We receive a "Failed to Open a Table" message from Profiler. Using the
SP1, SP2, SP3 version of the client tools (or the SP4 beta) on the same
tables does not exhibit any problem.

The table includes an ID column with an IDENTITY attribute that we use
internally. This has never caused a problem before. There's nothing
mentioned in the release notes or fix list.

Any guidance appreciated.

David Gugick wrote:
Opened a case with MS. For anyone interested:

The problem appears to be in the PFCLNT80.DLL trace helper DLL. For some
reason, this DLL will only open up a trace (saved as a table) if the
table contains a "RowNumber" column. "RowNumber" is only added via the
Profiler UI when using the Save as Trace Table option. It's not
something that's added automatically when performing a server-side trace
(although it can be manually added). When the column is missing from the
table, Profiler kicks out an error.

The problem did not appear in the SP4 beta and, in fact, does not appear
when the SP4 beta version of PFCLNT80.DLL is used in place of the SP4
release.

StoredProc Help...
The server encountered a stack overflow during compile time.
SP4 reports queries blocking on themselves?
Return a horizontal table for result
comparing text fields - Second try