Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Windows 2003 and Orion Syslog (7.7)

Has anyone got this to work? 7.7 is giving the same error that 7.6 did about not having .NET installed.

I was under the impression that .NET is intergated into the core files of 2003.

Any ideas?

Find more posts tagged with

Accepted answers

All comments

tpula

I ran into the same issue today. I unselected the Syslog service so I could complete the upgrade. I then called tech support. They instructed me on how to force the syslog service installation from the command line. No need to download any updates from Microsoft.

Todd ***
Network Engineer - CCNA/CCDA/CCNP
The Stanley Works

OK, I think I know the answer to this one now.

You have terminal services installed.

When Terminal Services is installed on 2003, it is always in Application Mode. Terminal Service Administration mode was replace with Remote Deskop.

Terminal Service will alter some key environmental variables to help protect the Windows\System32 directory.

If you run the following command

change user /install

This will put Terminal Service into install mode and put the environmental variables back to where the .NET framework can be found. After running this command, you can then start the Wizard and it will find the .NET Framework.

To turn off install mode, run the command

change user /execute

BK
Nobody Special