Local Computer Address Show in Client App Error - c#

I would like to know why this my computer address is showing in client computer application error.
why this one is happening, I have no idea.

This information comes from .PDB file which contains debug information, and it were generated during the compilation.
You might consider send your release code not debug code to your customer, which will remove the .PDB file.

Related

Elmah error logs show local env path while running on production server

I have a C# service application running on a production machine. The service's job is to sync with another API every 60 seconds. However recently some really bizarre errors started to show up.
The error message itself is pretty straightforward - failed entity validation.
However the path of the file in which the error occurred is the one I'm using when developing locally.
So the server path of the app is "C:/CronJobs/AppName/.." (1), while my local path is "C:/Users/MyLocalUsername/Local/Source/Repos/.." (2).
So the issue is the production server is throwing some errors, and then says that the error occurred in files in "C:/Users/MyLocalUsername/Local/Source/Repos/..", and this location doesn't even exist on the production server, it exists only on my local machine.
I've checked the Host name logged in the database and it's certain that it's coming from the production server. The database itself is protected anyway so I don't even have direct access to it, I have to RDP to manage it.
I restarted the application and it still persists (no errors thrown while it was turned off though).
Can somebody give me any clue where to look to resolve this problem?
I believe that those parts are actually added at compile time on the building machine. If you have debug symbols enabled on your build, these will go the the production environment when you deploy.
Look for PDB files on your production environment.

How to handle Outlook's “Outlook is using an old copy of your data file (.ost). Exit outlook and blablabla” error at an API level using VBScript?

I have created some automated scripts in VBS to execution some tasks automatically on a remote virtual machine. However, whenever I want to email the result to the people that it concerns, Outlook, on start, gives me this error, preventing me from sending any email. The script could not send anything until I manually dismiss this message (but I did not have to actually solve this). The client machine that sends email is a remote virtual machine. It is managed by a driver machine (another remote virtual machine) in such way that every time a new build comes out the client machine gets restored to a checkpoint and downloads the build and installs it and then tests it. It seems that since it is using a snapshot, the outlook data file will have to be out-of-sync with what's on the server, possibly causing the aforementioned error.
Does anyone know how to handle this error in VBScript? Thank you in advance!
You could try to avoid the use of outlook.ost at all. Turn off cached mode (for Exchange) or turn off any Send/Receive settings for folders. Close Outlook and rename outlook.ost to .old.
Open Outlook and check too see if outlook.ost is not created again.

Get better error detail on Azure deployment

I am feverishly trying to track down all of the new errors that deploying a new app to Azure creates. It would be greatly beneficial on Azure to get the same detail on the source error section of the error page that the local instance creates.
For example, on local I get:
But on Azure I only get:
So identifying which line is causing this issue is extremely difficult. Anyone know how to enable this?
Edit:
Below are the server 'Error Messages' configurations:
The line numbers are part of the pdb files, so if you already have pdb files deployed, it may be that these were not built together...try rebuilding and deploying the pdb files...
Have you tried deploying your app as a website rather than a web role? I don't recall seeing any less detail in error messages from our Azure websites than I was seeing locally. Also, have you considered something like Elmah?

how to make a process run on iis?

Dear all, i have following code to open a file on click of a button
System.Diagnostics.Process.Start("soffice.exe",filepath);
soffice.exe is to open .odt files & filepath is containing the complete path of the file which i want to open.
This is working perfectly when i m executing the code on my local system, but as i m hosting it on the iis server (5.1), its not taking any action (event not throwing any error too). My filepath is accessing a folder in my project, not outside. Kindly suggest the possible reasons and solutions
In response to your comment above...
First of all, by "web service account" I don't mean web services. I mean the service account on the web server under which the web application runs. This could perhaps be the account of the user logged in to the website, or the default IIS account, etc. The best way to address this would be to fully qualify the path to soffice.exe when calling it, that way you don't have to worry about the PATH environment variable. (Additionally, you don't have to worry as much about another application being run maliciously or by accident and doing something unexpected with unknown permissions.)
Second, there seems to be a critical design flaw in your approach. Even if you do manage to get the application to launch on the server, it's going to launch on the server. Is the resource manager sitting at the actual web server? If not, then opening the file in the application on the server will do him no good whatsoever. If he is sitting at the server, then he's the only person who can use this.
You don't want to open the file on the server. You want to deliver the file to the client. Then if the user (the resource manager in your example) can open the file in soffice.exe on his local machine. If his environment is set up correctly, it should open automatically. (Though the browser will also give him the option to save the file locally and then open it.) Simply linking to the file should suffice. Is there any particular reason why it wouldn't?
If you need to use a form post rather than simply a link in order to deliver the file, you can still stream the file from your server-side code. Here's a previous question discussing how to do that. Basically the process involves clearing the output buffer, setting the headers (content length, content type, suggested file name, etc.), streaming the bytes, and flushing/closing the output buffer.

Log4Net on Godaddy Shared Host

I had Log4Net working on my Local machine. It logged to a DB with one FileAppender, Nothing logged to a file. When I moved my code to my shared Hoting provider (GoDaddy) I got an exception about FileIOPermission required.
Does anyone have any ideas of what might have been happening?
I removed the configuration and am at the moment using ELMAH to log everything, (although I would like to use Log4Net) so I don't have any of the examples or stack traces anymore.
Any thoughts would be appreciated.
This is not much info to work with, but here are a few things you can do:
You can always debug the actual log4net code.
When it doesn't write to a file, it's usually a problem of
permissions. If it's a web project,
look at what user the application
pool is running under (usually LOCAL
SYSTEM), and that user needs write
access to the file (and the
directory where you want to put the
file). The fact that the exception
is actually FileIOPermission
required definitely points to this
direction.
Similarly, it might be that there is a temp file that log4net is
trying to use when you're logging to
a db. In that case, you might going
to have to change your temp folder.
Furthermore, look at this post:
Log4Net works on Dev machine, fails when deployed to shared host (using same db/connstring)

Resources