Can't Install in Win2008R2

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run Setup.exe or SetupSyslogDaemon.msi 
2. after input 2 pages sql server information
3. will pop-up a dialog: "The installer has encountered an unexpected error 
installing the package. This may indicate a problem with this package. The 
error code is 2869"

This is a good software for syslog. It's work fine in win2003. Please help fix 
Win2008 install problem. Thanks a lot. :)

Original issue reported on code.google.com by jdp...@gmail.com on 21 Jul 2011 at 2:27

[GoogleCodeExporter]

I second this. OS WinServer2003 SBS, MSSQL Express 2008R2. Exactly the same 
steps, exactly the same result.

Original comment by p...@otenet.gr on 11 Aug 2011 at 7:19

[GoogleCodeExporter]

I have the same problem.

Original comment by fmunt...@gmail.com on 16 Jan 2012 at 6:22

[GoogleCodeExporter]

I had the same problem.

you MUST use different credentials for the 2 sql-information pages.

Original comment by michkalc...@gmail.com on 18 Feb 2012 at 3:13

[GoogleCodeExporter]

I did get it to install on Server 2008 R2/SQL Express 2012 with some changes 
and using one of the recommendations from this issue.

1) The setup.exe in the SyslogDaemon folder must be set to run in Compatibility 
Mode for "Windows XP (Service Pack 2).  In addition you must check "Run this 
program as an administrator" if UAC is enabled.

2) It seems to be true that you must use different credentials for each SQL 
information page.  I had installed SQL with Windows Authentication only, so 
that had to be changed to mixed authentication.  I created a syslog user for 
event addition to the database.  So, on the first screen I used Windows Auth 
(leave the username and password fields blank) to create the DB as me, then on 
the second screen I used the SQL account I created to insert the event logs.

For the web client piece, things are a bit more touch and go.  Again, 
compatibility mode must be set to "Windows XP (Service Pack 2)" and "Run this 
program as an administrator" must be checked if UAC is enabled.

If you are using IIS 7 (or IIS 7.5 I assume) you will also need to install the 
"IIS 6 Management Compatibility" role feature to prevent an error where the 
installer will start and then fail immediately.

The issue is that this will still not allow the program to "install" for some 
reason.  What I did to get it to install somewhat correctly is create a batch 
file to run the provided MSI file with logging enabled.  The command I used was 
"msiexec /i SetupSyslogWeb.msi /L*V install.log".  This will start the install 
with a log file created.  Again, you must use separate credentials for the 
table creation and data insertion - I followed the convention I specified for 
the daemon process.

The install will progress and you will receive a message stating the installer 
failed with the 2869 error, however, if you check the IIS root you should see 
that the files were actually installed correctly to the directory you specified 
in the installer.  I don't know why this works or why it only seemed to work 
for me with logging specified.

The problem is the files are present, but not configured.  You will need to add 
the database configuration string to the Web.config for the website.  You can 
get the correct string from the daemon installation directory in the 
"SyslogService.exe.xml" file if you open it with a text editor.  Copy 
everything between the quotes after the "connectionString" property and paste 
it in between the quotes to the "connectionString" property in the  Web.config 
for the web site.

The last step to get the web site up and running is to open IIS Manager, locate 
the site and directory you specified in the web portion installer (mine was 
Default Web Site\Syslog as an example), right-click the correct directory and 
choose "Convert to Application" from the context menu.  If you choose to test 
it when the info box is presented it will fail - don't worry about it.  Once 
the application conversion is done the icon should have changed from a folder 
to a globe.  Now you can browse to http://localhost/Syslog/ (or whatever you 
named your directory) and see the list of events that have been transmitted.

Sorry for the wall of text I just thought it might help someone out.  Looks 
like a decent product.

Original comment by eram...@gmail.com on 3 Oct 2013 at 8:30

[GoogleCodeExporter]

Unfortunately I still get the 2869 despite following your steps for installing 
the daemon.  What rights / priv's did you grant to the database user, the 
account to be used for normal runtime use?

Also did you install for all users or just the current user?

Thanks

Original comment by prdug...@gmail.com on 4 Oct 2013 at 12:03

[GoogleCodeExporter]

Sorry I didn't see this earlier.

The database user was a regular SQL account with sysadmin privileges.  I don't 
know if it needs to be that permissive but it needs to read and write to the 
database.  You probably can get away with less.  I don't know a lot about SQL 
Server so I just went all out right away.  My account was used to create the DB 
and that account was also a sysadmin for SQL.

I installed for the current user but I had tried both ways before switching to 
separate accounts and received the 2869 error so I don't think it matters 
either way.  You can try it both ways and see what works.

I ended up wanting some extra features for the web interface so I wrote a 
custom web interface that only displays events from the last three hours on the 
default page and also allows you to search all records by keyword or date 
range.  It also doesn't require an installer package so if you can get the 
daemon to install you can just create an IIS site for the .aspx/C# files and 
you are off and running.  Should avoid some of the web console problems people 
are experiencing with Server 2008 R2.

Not sure how to contribute to this project but maybe if the owner sees it and 
is interested I can send the stuff to him.  It is my first C# project and it 
probably sucks pretty bad as I am still learning this development stuff so it 
probably could use a once-over by someone who knows what they are doing.

Original comment by eram...@gmail.com on 13 Nov 2013 at 10:57

[GoogleCodeExporter]

I could install it on Windows 2008 R2. That's how I did it:
1. Installed IIS role with ASP.NET and IIS 6 compatibility
2. Installed SQL Server with Windows authentication
3. Created an additional Windows account and granted dbcreator permissions in 
the SQL
4. Installed Aonaware syslog daemon providing it the previously created account
5. Granted permissions to IIS APPPOOL\DefaultAppPool user account, assigned the 
syslog_iis schema
6. Installed Aonaware web service with no account provided
7. ??????????
8. PROFIT!!!!!!

But now I have some problem with international characters - they are showing 
question marks instead of readable characters even when I fetch message table 
from SQL directly, though the syslog source is sending them to the network 
correctly (I saw it with the sniffer)

Original comment by no4...@gmail.com on 15 Nov 2013 at 2:38

[GoogleCodeExporter]

Hello again! :) Today I finished reworking of a source code of Syslog Daemon. 
Now it is able to send and receive international characters in MSG field - I 
hard-coded CP1251 there, still keeping the RFC3164 confirmity. Next step is to 
make usable reports in SQL Reporting Services, but it is usable right now for 
our needs :) Thanks to the author for a good job!

Original comment by no4...@gmail.com on 25 Dec 2013 at 12:56

[GoogleCodeExporter]

I got WHS 2011 (64 bit) with SQL Server 10.0.5512 and the installs ends with 
"The error code is 2869".

Windows XP mode, same result
Different cred, same result
No firewall, same result

what next?

Original comment by tomasens...@gmail.com on 18 Mar 2015 at 8:48