tag:blogger.com,1999:blog-20196010.post2848736577643088087..comments2023-04-02T10:19:37.644+02:00Comments on Frederik Gheysels' DevLog: Cannot open log for source {0} on Windows 2003 ServerFrederik Gheyselshttp://www.blogger.com/profile/15416462808733991725noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-20196010.post-36544892631662662772008-08-08T18:55:00.000+02:002008-08-08T18:55:00.000+02:00I've never experienced this problem on Vista. (I ...I've never experienced this problem on Vista. (I never tested it as well).<BR/>Do you run VS.NET as administrator on Vista ?<BR/><BR/>Maybe you can try this registry hack on your Vista machine, and see what happens ?Frederik Gheyselshttps://www.blogger.com/profile/15416462808733991725noreply@blogger.comtag:blogger.com,1999:blog-20196010.post-24860261268380070992008-08-08T17:21:00.000+02:002008-08-08T17:21:00.000+02:00Hi, does this issue apply to Vista (home premium) ...Hi, does this issue apply to Vista (home premium) systems as well as to Win 2003 server? <BR/><BR/>I recently installed VS 2008 express on my personal Vista home premium machine and my son's XP SP2 machine. When attempting to create a SQL express datasource through C# for instance, on the XP it creates fine. On the Vista, I get the error.Anonymoushttps://www.blogger.com/profile/03163589256974994480noreply@blogger.comtag:blogger.com,1999:blog-20196010.post-56913209709388667292008-02-26T20:51:00.000+01:002008-02-26T20:51:00.000+01:00I've corrected it. Thanks for pointing it out.I've corrected it. <BR/>Thanks for pointing it out.Frederik Gheyselshttps://www.blogger.com/profile/15416462808733991725noreply@blogger.comtag:blogger.com,1999:blog-20196010.post-73581474038194704932008-02-26T03:40:00.000+01:002008-02-26T03:40:00.000+01:00Hi Frederik, you have a small typo in your sugeste...Hi Frederik, you have a small typo in your sugested solution for this problem. You have written '...append the following string to the existing value: (A;;0x0002;;AU)'. <BR/><BR/>However, the actual value is missing a semi-colon and it should be (A;;0x0002;;;AU), otherwise the System Event Log raises the following error;<BR/><BR/>Event Type: Error<BR/>Event Source: EventLog<BR/>Event Category: None<BR/>Event ID: 6015<BR/>Date: 26/02/2008<BR/>Time: 10:06:56 AM<BR/>User: N/A<BR/>Computer: servername<BR/>Description:<BR/>The custom security descriptor for the event log Application is invalid. Please ask an administrator to correct the CustomSD value in registry for this event log.Anonymousnoreply@blogger.com