Showing posts with label thisi. Show all posts
Showing posts with label thisi. Show all posts

Friday, March 9, 2012

Publishing Web Application

Hello to everybody.

I got a problem like this:

I developped a project using Visual Studio 2005 Standard Edition on a XP pro x64 Machine using a developpemet data area on a SQL 2005 Express Edition.

Everything is ok, even the user and profile management. But when I try to publish my application on IIS (we're talking about a little Intranet), I get my problems. I think is important to say that the server is a Windows Server 2003 and data (database reproduced as a backup of the developpement one) are under an SQL 2005 Standard. The strange thing is that by publishing the "site" VS create a DB under SQL Std named with the path of local ASPNETDB.MDF.

I can reach everything, all data are ok, but when I pass the login page going to main menu on my web-application, I get this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I think the problem is SQL STD and the fact that it's not "able" to manage MDF files.

I even tried to re-map the SQL DB (named simply as ASPNETDB on the SQL std) by adjusting the web.config file on connection type and user and password to reach the DB ASPNETDB but it does't work anyway.

Can anybody solve my problem?

Thank You

Can you post your connection string please|||

This first is the original connection string in web.config defined in the developpement area:

<add name="ASPNETDBConnectionString1" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>

This one is the connection to the server (SQL STD):

<add name="ASPNETDBConnectionString1" connectionString="Data Source=SERVER\SQLSERVER;Initial Catalog=ASPNETDB;Persist Security Info=True;User ID=user;Password=password" providerName="System.Data.SqlClient"/>

Thank You.

Mauro

Monday, February 20, 2012

PSSDiag Failed to instantiate an XML DOM

Can anyone explain to me what I need to do to correct this?

I have ran the SAME PSSDiag install from the this particular server MANY times before.

All of a sudden, it now fails to start and I find this error, that is posted in teh subject line of the thread, in teh Windows Application Event Log.

If I need to install another app in order to correct this, please let me know if the installed app will need a reboot of the server to take affect. I have to schedule down time for that.

Thanks ALL!

Check with this
http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en

PSSDiag Failed to instantiate an XML DOM

Can anyone explain to me what I need to do to correct this?

I have ran the SAME PSSDiag install from the this particular server MANY times before.

All of a sudden, it now fails to start and I find this error, that is posted in teh subject line of the thread, in teh Windows Application Event Log.

If I need to install another app in order to correct this, please let me know if the installed app will need a reboot of the server to take affect. I have to schedule down time for that.

Thanks ALL!

Check with this
http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en