WynApse

After the Altiris-a-rama was complete, I finally got back to this.

Very possibly the workstation was in a 'weird mode' Friday, Monday AND yesterday during my other problems, <start spin> but it doesn't excuse the other things that were going on surrounding Crystal Reports, e.g. the Exception message</start spin>

I worked as if I only had one shot to get it right:

• Got a Diet Dr. Pepper and 2 Extra-Strength Excedrines
• Refreshed from Version Control
• Modified the element I wanted to replace in the xsd, all the way to desired end result
• Deleted the xsx and cs files, then saved the xsd to reproduce them
• Close Project, Exit VS
• Reopen both, open the rpt file, go to the main report, right-click, Database->Set Location and pick the Visual Studio Class then pick the ds name in both boxes and hit the Replace button
• Close Project, exit VS (because the Field Explorer still showed the original)
• Reopened both, went to the subreport, and Field Explorer was now correct. Drag both new fields to the report, take the defaults for now
• In the code behind, modified the query to read from my new table
• Press F5 and pray (at this point, the pray part is more important than the above)
• It works!
• Very carefully modify the rpt visual effects to get the two new fields the way I want them and get the Heck out of the code

I did a complete release rebuild and tested, Saved to Version Control, deployed it to the Intranet, and tested it there to be correct before I took a really deep breath.

What a deal... glad it works... on to more fun things!

Working on-site for a client that has a pretty restrictive approach to computing in general. I can get to most places I need to, so it's not a huge problem, but it's out there burning cycles for me all the time.

They use Altiris to manage updates and who knows what else out to the 6000+ workstations. It's got to be a huge headache, and something I wouldn't want to approach, but it's not helping me much right now.

I have two workstations on my desk.. an older Win2K box that is still used for development mostly because there are still folks I support that are running 2K, and an XP box that is new as of last Thursday.

When I logged into them this morning, the Win2K box went straight to AeXNSAgent.exe running 100% of the CPU. It's been that way an hour and a half! I called the help desk and they're going to have to send someone around because "when it gets into that mode" they can't log into the box remotely... duh... I can't do very much from my side either! Wonder how much life it's taking off the processor running at 100% for that long...

Since the development tools and version control software and, and, and, are all on that box, I'm still waiting. I hope when they get here, they do more than "End Process" on that.

I'd have killed it myself earlier, but who knows what it's doing, and if I do, is it going to have to start this process all over again next time... sigh...

Just found out I have a 1:30-2:30 appointment with the desktop folks so that they can look at this. I should have brought a deck of cards! Hope it doesn't smoke the CPU between now and 1:30...

1:50 finally saw the end of it... roughly 4-1/2 hours. Uninstall/reinstall of the Altiris software to resolve.