![]() ![]() You can read here how to set internal debugging: if anything is wrong with your connection string- it will log this. If the connection cannot be established (as seems the case) -e.g. Try enabling this and (re-)start your application. I have also set the db_owner permission on the User.Īssuming that you already checked that the configs of local and staging are in sync: did you try with log4net internal debugging? When log4net is working on one location and not on the other this has helped me a few times. Moreover, I have setup a profiler to see if there are any request coming through but in vain. I have also tried to modified the nfig directly and use the following configuration: īut still it worked on my local instance and not on the Staging Server. However, on the Staging Environment, no errors are being logged. The same configuration has been applied on my local instance and everything works, i.e, the errors are logged into the table Log. However, the errors are not being logged into the database. I am using the Log4Net to insert errors into MSSQL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |