Just curious if anyone else has run into anything similar...
A few weeks ago, I tried to compress an FGDB. The process hung for 20 minutes, so I killed it (small FGDB should have taken a few minutes at most). After that, my PC has problems accessing any FGDB on a network drive. Even when I copy data from SDE to a brand new FGDB on the network, it takes over an hour (usually takes sub 5 min). Anything to do with an FGDB is slow or not working right. If I put the FGDB on the C:drive, it works fine. If I use a PGDB on the network with the same tests, no problems. I upgraded to v10 (from 9.3) and the problem persisted.
As a real kicker, the compress problem occured on my old PC. Last week, I got a new PC, fresh OS, and a fresh GIS install (back to 9.3). According to IT, they only copied over my "c:\downloads folder, My Documents, Favorites, and Desktop items to the new computer". However, the problem followed to my new PC. Other users have the same problem on my new (and old) PC. I have no problem on other PCs. I can't imagine what would have followed to the new PC based on what was copied, especially that only affects the FGDB format.
I've logged this with support, but no answers yet. Just curious if anyone else has seen anything similar?
Thanks, Gavin