Re: Connection Problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Jonathan,

I would suspect the installation as a whole is not happy after the switch
from Express to Full. I doubt any post-install patching or fiddling will
really get it truly corrected.

While it would be a real pain, I would suggest your best bet would be to
rebuild your dev PC from scratch.

If you have the luxury of access to a spare PC (I know this may not be the
case), you could build a clone of your PC so you're not entirely without a
system while all the installs occur and you can more easily check what
settings you had before.

This does have the advatnage of completely cleaning your registry and
provides an opportunity to avoid installing anything you no longer require,
thus giving you a pristine enironment that operates smoothly (at least until
refilled with daily accumulated grunge).

I was forced to do this full rebuild approach due to a hard-disc failure,
ended up upgrading my disk from PATA to SATA and capacity from 80Gb to
250Gb, very cheaply. Speed differences on system boot and program compiling
were noticably improved using the SATA drive, so there were tangible
benefits there too.

Fortunately I already had a note of the majority of my installed programs.
For my config, this took about a day of disk shovelling. I then imaged my
system in its clean state to DVD using Ghost 2003 (fantastic program!) so
that in the event of any further issues I wouldn't have to sit and shovel
discs for so long. You can extract individual files from the Ghost image
set if required.

I keep my Visual Studio project files backed up on a server (I run a simple
batch file every day to xcopy them over), so restoring my projects wasn't
too painful - just had to remember to recreate the local IIS virtual
directories, which was easy enough. The source control wasn't quite so
simple, but it wasn't too bad either (I'm using an old-ish version of
SourceGear Vault).

It may be worth noting that I don't run a local copy of SQL Server. Instead
I have a DEV instance running on a real server on the network. This has the
benefit of not needing to load all the SQL processes and services, which all
consume resources of a (in my case) pretty heavily loaded PC.

Not a direct solution and perhaps something of a sledgehammer approach, but
it should certainly fix the problem!

Regards,

Alec


"Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx> wrote in message
news:%23ttaDVMWIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
I'm a long-time programmer new to server administration and SQL. For some
reason, this stuff just doesn't seem to ever work for me.

I'm developing an ASP.NET application in Visual Studio 2008. I recently
upgraded from SQL Server 2005 Express to SQL Server 2005 (with SP2).

It took Microsoft technical support about three hours to figure out why
SQL
Server Management Studio was unable to log onto SQL Server, so I can
finally
do that. (The proper accounts were not created.) But I am unable to access
SQL Server from Visual Studio.

1. In VS2008 Server Explorer, I was able to modify the database connection
so that it works with SQL Server 2005 instead of SQL Server Express.
However, every time I reload Visual Studio, I have to make these changes
again. Does anyone know how to get VS2008 to remember these settings?

2. When I select the ASP.NET Configuration command, it's horribly slow and
tells me there are no longer any users. (I can see them looking at the
aspnet_Membership table.) It also now calls the application "/<appname>"
whereas before it was just "/".

Under the Security tab, it says:

"There is a problem with your selected data store. This can be caused by
an
invalid server name or credentials, or by insufficient permission. It can
also be caused by the role manager feature not being enabled. Click the
button below to be redirected to a page where you can choose a new data
store.

The following message may help in diagnosing the problem: 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)"

When I click Choose Data Store, I have the option of "Select a single
provider for all site management data" and "Select a different provider
for
each feature (advanced)".

I choose the first one and I get a page that says No providers created.

I'm also struggling with the connection string but maybe that's working
and
it just doesn't recognize anything because of the problems described
above.

Does anyone know what happened here, or how I might try and troubleshoot
it?

I'd appreciate any input.

Thanks.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com



.

Quantcast