- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: Altiris SIDgen Service "WARNING Unable to open...
ProLiant Deployment and Provisioning
1748232
Members
3350
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 11:26 PM
тАО11-07-2007 11:26 PM
Altiris SIDgen Service "WARNING Unable to open log file name specified"
When I'm creating an image from my servers I keep receiving the error:
Altiris SID Service
"WARNING Unable to open log file name specified"
Using Default Log File Name Instead.
This only occurs once the image has been taken and the configuration is being restored.
Any ideas as to what is causing this? It is stopping the automation part of this process as I have to click OK for it to continue.
Thanks in advance.
Altiris SID Service
"WARNING Unable to open log file name specified"
Using Default Log File Name Instead.
This only occurs once the image has been taken and the configuration is being restored.
Any ideas as to what is causing this? It is stopping the automation part of this process as I have to click OK for it to continue.
Thanks in advance.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 03:32 AM
тАО09-10-2008 03:32 AM
Re: Altiris SIDgen Service "WARNING Unable to open log file name specified"
Delete C:\Sidgen.log before taking the image, this should resolve the issue.
Regards,
Tim
Regards,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2008 02:08 AM
тАО10-23-2008 02:08 AM
Re: Altiris SIDgen Service "WARNING Unable to open log file name specified"
The same thing's happening when capturing or deploying images to and from my Citrix application servers with remapped drives (J & K instead of C & D). Using RDP 3.81. There is no C:\sidgen.log, no J:\sidgen.log, no sidgen.log anywhere on the target server.
I think maybe it's trying to create c:\sidgen.log or similar, but can't because there is no C: drive. Or maybe it's an Aclient log? Logging is turned off in Agent Settings on the RDP server, with the setting to force new clients to take these settings currently enabled. Is there a way I can turn off this logging, so it doesn't even try to create the log file after image capture or deployment?
It progresses fine after clicking Ok, letting it reboot, and clicking Ok again when the message reappears.
Also, it doesn't happen when restoring images taken with an older RDP build based on RDP 3.50. But if I subsequently capture the same server, the problem is back. It seems to be related to updating the Aclient on the target, or possibly some new Aclient settings, when a server is deployed using the new version of RDP.
Can anyone help?
I think maybe it's trying to create c:\sidgen.log or similar, but can't because there is no C: drive. Or maybe it's an Aclient log? Logging is turned off in Agent Settings on the RDP server, with the setting to force new clients to take these settings currently enabled. Is there a way I can turn off this logging, so it doesn't even try to create the log file after image capture or deployment?
It progresses fine after clicking Ok, letting it reboot, and clicking Ok again when the message reappears.
Also, it doesn't happen when restoring images taken with an older RDP build based on RDP 3.50. But if I subsequently capture the same server, the problem is back. It seems to be related to updating the Aclient on the target, or possibly some new Aclient settings, when a server is deployed using the new version of RDP.
Can anyone help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2009 05:08 AM
тАО07-20-2009 05:08 AM
Re: Altiris SIDgen Service "WARNING Unable to open log file name specified"
Hi there.
The logfile is specified in the following Registry string: HKLM\Altiris\SIDgen\LogFileName
Even though you specify not to create a logfile, you still get an error message when the LogFileName specified is pointing to a none existing location. For example C:\SIDgen.log on a Citrix server that is configured with remapped drives.
All you have to do is change HKLM\Altiris\SIDgen\LogFileName to an existing logfile location and try again.
Good luck!
The logfile is specified in the following Registry string: HKLM\Altiris\SIDgen\LogFileName
Even though you specify not to create a logfile, you still get an error message when the LogFileName specified is pointing to a none existing location. For example C:\SIDgen.log on a Citrix server that is configured with remapped drives.
All you have to do is change HKLM\Altiris\SIDgen\LogFileName to an existing logfile location and try again.
Good luck!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP