FIX: SQL 2000 Error 18483

Over the past few days, some of our users have informed us that they have encountered SQL 2000 error 18483.

Recommended: Fortect

• 3 minutes before aria-label = “Article read.

In This Article

Details

Explanation

This happens when a person tries to set up a replication representative on a system that has been updated using a disk image of most other computers on which the SQL situation was originally installed. An error message similar to the following is documented for the user:

SQL Server Management Studio was unable to configure “ “for the” “distribution list. Error 18483: Unable to connect to web hosting server ‘ ‘ because ‘Distributor_admin’ is not installed when connecting to the Internet remotely. Make sure you have the correct login as indicated. %. * ls.

Reason

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

If you are deploying SQL Server from a CD image of the hard disk of another computer that has SQL Server installed, the computer’s network tag with the image will be saved in the new installation. An incorrect network name will cause the configuration to point to the replication distributor to fail. The same problem occurs if you rename the computer after installing SQL Server.

User Response

To work around this issue, replace the SQL Server username with the correct network name on the computer. To do this, follow these steps:

1. Log on to the computer where you completely mounted SQL Server from a disk image and then processed the following Transact-SQL statement in SSMS:

   

     - use the main databaseUSE the wizardWALK- Declare local transfers      DECLARATION @serverproperty_servername varchar (100),@ varchar servername (100);- Get the value returned by the SERVERPROPERTY system functionSELECT @serverproperty_servername = CONVERT (varchar (100), SERVERPROPERTY ('ServerName'));- Get return value @@ SERVERNAME due to global variableSELECT @servername = CONVERT (varchar (100), @@ SERVERNAME);- Remove server with wrong nameEXEC sp_dropserver @ server = @ servername;- Add correct server as local serverEXEC sp_addserver @ server = @ serverproperty_servername, @ local = 'local'; 

2. Restart the SQL Server computer.

3. To verify that the specified SQL server and network name are the same for all computers, run a Transact-SQL statement:

     SELECT @@ SERVERNAME, SERVERPROPERTY ('ServerName'); 

Additional Information

You can use the global number @@ SERVERNAME or the SERVERPROPERTY (‘ServerName’) function in SQL Server to detect that the computer network tag is running on SQL Server. The ServerName property of the corresponding SERVERPROPERTY function automatically reports when the computer’s network name changes, such as when the computer restarts and the SQL Server service. Variable element @@ SERVERNAME retains the original SQL Server computer name until the SQL Server name is manually reset.

Steps To Reproduce The Problem

On the machine where you deployed SQL Server from a good hard disk image, do the following:

1. 

   Start Management Studio.

2. In Object Explorer, the name of the instance of the SQL Server assembly.

3. Right-click that specific replication folder and select Configure Application Replication, then click Configure Publishing, Subscribers, and Distribution.

4. In the Deployment Configuration Wizard dialog box, click Next.

5. In the new mailing list, click on the element to make sure it is your own mailing list; SQL Server creates a distribution database and radio button for the wagon, then clicks Next.

6. Click the Next box in the appropriate SQL Server Agent startup dialog box.

7. Click “Next” frequently in the snapshot folder.

   Note

   If you receive one message confirming a snapshot of the directory path gu, click “Yes”.

8. In the Distribution Database dialog box, click Next.

9. In the My Editor dialog box, click Next.

10. In the Action Wizard dialog box, click Next.

11. In a kind of dialog box, just click Finish to complete the wizard.

See Also

• Rename the computer that hosts the stand-alone instance of SQL Server
• @@ SERVERNAME (Transact-SQL)
• SERVER PROPERTY (Transact-SQL)
• sp_addserver (Transact-SQL)

If you receive your own message confirming that you can take a snapshot, click Yes in the folder.

I have implemented trans-replication linking SQL 2005 (subscriber) and SQL 2000 (publisher).

When I configure the distributor, I enter the error: 18483 may not connect to server “GHS0023RPT” because “distribution_admin” is not configured as an online restore connection to the server.

I search the community forum and find many answers, but still useless.

1. I have already configured the server alias in sql 2000 and only in sql 2005.

2. In sql 2000. I am checking the Windows Server 03 property. The computer name is “GHS0023RPT”.

I might be a little late with this important answer, but I noticed the impact on the computer name and (element2) @@ servername (element3). If that’s all you’ve done, you can run the following script. This will fix the error. You may need to stop and start SQL.

So you mean that the Windows machine name and the SQL server name really have to be the same when creating the distribution?

I feel like I ran into a similar problem when my preferred computer name is “IP-0AC11DDC”, the SQL server name is “SQLSERVER1”

When I tried to make this server a distributor, the idea tried to connect and “IP-0AC11DDC” and the message “Microsoft SQL Forum, Error: 18483” could not connect to “IP-0AC11DDC” because “Distributor_admin” was not intended for remote connection to any type of server.

Your family stops replicating the PULL transaction database with a remote wholesale sender, or

Erro Sql 2000 18483
Sql 2000 Oshibka 18483
Sql 2000 Fel 18483
Sql 2000 Fout 18483
Blad Sql 2000 18483
Error 18483 De Sql 2000
Erreur Sql 2000 18483
Sql 2000 Fehler 18483
Sql 2000 오류 18483
Sql 2000 Errore 18483

Justin Fernando

Related posts:

Steps To Fix MS Script Editor Error The Best Way To Solve Anger Error 202 Solutions For Permanent Stationary Position Error Tips To Fix Removing Drive C In Windows XP