StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLog4Net working locally but not on remote Azure DB
primarykey
Id
17104851
data
AcceptedAnswerId
17106229
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-14T09:02:06.510
FavoriteCount
0
LastActivityDate
2013-06-14T10:17:34.583
LastEditDate
LastEditorUserId
0
OwnerUserId
196189
ParentId
0
PostTypeId
1
Score
1
ViewCount
679
LastEditorDisplayName
text
Body
I locally develop an ASP.NET MVC application and use Log4Net to log message on the local database with the following connection string (log4net.config): <pre><code><connectionType value="System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <connectionString value="Data Source=.\;Initial Catalog=MyDatabase;Integrated Security=True" /> </code></pre> This is perfectly working (database entries are appearing in the Log table). Now I'd like to log to remote azure database server, so I just changed the connection string into following: <pre><code><connectionString value="Data Source=mydb.database.windows.net,1433;Initial Catalog=MyDatabase;User ID=username@mydb;Password=mypassword;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" /> </code></pre> I inserted my IP address in the firewall (as proof I can connect via SQL Studio on my machine to the azure db instance). When debugging the application I don't see any exception caused by log4net. I use castle-windsor to inject the ILogger where needed, here is my Installer: <pre><code>public class LoggerInstaller : IWindsorInstaller { public void Install(IWindsorContainer container, IConfigurationStore store) { container.AddFacility<LoggingFacility>(f => f.UseLog4Net().WithConfig("Configuration\\log4net.config")); } } </code></pre> The database on the azure DB instance is the exact copy of the local one (same create script). But nothing appears in the remote database. What am I doing wrong? How can I find out the problem? Thanks a lot
Tags
<asp.net><azure><log4net><castle-windsor>
Title
Log4Net working locally but not on remote Azure DB
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWizche
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POLog4Net working locally but not on remote Azure DB
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.