ERROR 26 AFTER UPGRADE OF SQL 2005 SERVER EXPRESS

I cannot make connection to database that I was using prior to the upgrade of SP1. Keep getting error 26-default settings prohibit remote access - but it's not remote.? Can anyone help - tell me how to change defaults or change properties to connect to my data after the update?

I am using Visual Web Developer Express. It can see the instance but cannot connect.

Using TCP/IP rather than named pipes is always "remote". YOu can enable the remote connections on the Computer by using the SQL Server Configuration surface. See more details and a screencast at my site in the section Screencasts >Enabling remote connections

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Thank you - this did it.

Error 21776: PUBLISHER_NAME not found in DistributionPublishers collection

While trying to set up remote distribution on server PUBLISHER_NAME, I
get the above error when trying to specify the remote distributor.
(Error 21776: PUBLISHER_NAME not found in DistributionPublishers
collection on DISTRIBUTOR_NAME)
However, I have set up distribution on DISTRIBUTOR_NAME, and in the
Publishers tab of that window, I have checked the entry for
PUBLISHER_NAME. The alias for that server matches exactly the
PUBLISHER_NAME.
Do I need to restart the SQL Server for this entry to be acknowledged?
Is there some other step of configuration I am missing? Why doesn't the
PUBLISHER_NAME see that it's name is indeed on the authorized publisher
list for DISTRIBUTOR_NAME?
Thanks in advance for any help,
Jason
Its hard to say. Can you connect with your distributor and issue the
following commands for me. Post the results back here.
On your distributor
sp_helpdistpublisher 'RemotePublisherName'
On your remote publisher issue the following
sp_helpdistpublisher 'RemotePublisherName'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<iaesun@.yahoo.com> wrote in message
news:1112369037.970196.9940@.l41g2000cwc.googlegrou ps.com...
> While trying to set up remote distribution on server PUBLISHER_NAME, I
> get the above error when trying to specify the remote distributor.
> (Error 21776: PUBLISHER_NAME not found in DistributionPublishers
> collection on DISTRIBUTOR_NAME)
> However, I have set up distribution on DISTRIBUTOR_NAME, and in the
> Publishers tab of that window, I have checked the entry for
> PUBLISHER_NAME. The alias for that server matches exactly the
> PUBLISHER_NAME.
> Do I need to restart the SQL Server for this entry to be acknowledged?
> Is there some other step of configuration I am missing? Why doesn't the
> PUBLISHER_NAME see that it's name is indeed on the authorized publisher
> list for DISTRIBUTOR_NAME?
> Thanks in advance for any help,
> Jason
>
|||i'm very sorry for taking so long to get back to you. i was told to
stop setting up publishing and be a developer for a couple of weeks.
but that's over now, so i am back to this task.
firstly, thank you very much for your help, here are the results you
requested to see:
sp_helpdistpublisher 'RemotePublisherName' run on the distributor
reported:
"The remote server does not exist or has not been designated as a valid
publisher."
sp_helpdistpublisher 'RemoteDistributorName' run on the publisher
reported:
'RemoteDistributorName' is not configured as a Distributor.
however i have verified that on RemoteDistributorName that
RemotePublisherName is listed in the Publishers tab of the "Publisher
and Distrubutor Properties" window, and it is checked as a valid
publisher.
jason

Error 21007 Cannot add remote distributor

Hello,
I've been trying to set up an msde database for replication. I've fixed
some problems but I can't get past thisone. I've read every topic about
this error but nothing worked.
I've set up msde with 'setup SAPWD="***"', I didn't set the instance
name or any other parameters.
Thanks.
Thijs
http://www.imm.be/
I've solved the problem.
I registered the server as 192.168... and not as 'servername' in the
enterprise manager.

Error 21007

I can't configure my Sql Server 2000 Publisher, the Enterprise Manager
reports this error message: "Errore 21007. Cannot add the remote Distributor
when it tries to complete the operation. Make sure that the local server is
configured as a Publisher at a Distributor". What does it depends on? How can
I solve it?
Thanks.
Is this a local or remote distributor?
Its hard to fix these errors. IIRC I have been able to fix them by disabling
replication, un-registering SQL Server through EM, reregistering it as .,
bouncing the server, removing it from EM, registering it as the servername,
bounce, and trying again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ago" <Ago@.discussions.microsoft.com> wrote in message
news:ECC6DE78-1321-4BBD-BA7D-158639B07D3B@.microsoft.com...
> I can't configure my Sql Server 2000 Publisher, the Enterprise Manager
> reports this error message: "Errore 21007. Cannot add the remote
Distributor
> when it tries to complete the operation. Make sure that the local server
is
> configured as a Publisher at a Distributor". What does it depends on? How
can
> I solve it?
> Thanks.
|||It should be a local distributor.
I explain better my SQL server configuration.
I have a server named ITDEXANET001 and I have created a SQL server
registration with the server name ITDEXANET001, then I try to configure
ITDEXANET001 as Distributor and Publisher and I get this error message when
it is going to create the Distributor. I don't know if it is important but I
have also noticed that it adds an item in the Remote Servers folder named
LG696-EURO_J05 (that is the name of the domain), if I delete this Remote
server the installation of Replication fails with the error message 18482:
"Could not connect to server 'ITDEXANET001' because
'LG696_EURO_J05' is not configured as remote server", it is not clear to me
what it means.
"Hilary Cotter" wrote:

> Is this a local or remote distributor?
> Its hard to fix these errors. IIRC I have been able to fix them by disabling
> replication, un-registering SQL Server through EM, reregistering it as .,
> bouncing the server, removing it from EM, registering it as the servername,
> bounce, and trying again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ago" <Ago@.discussions.microsoft.com> wrote in message
> news:ECC6DE78-1321-4BBD-BA7D-158639B07D3B@.microsoft.com...
> Distributor
> is
> can
>
>