Showing posts with label machines. Show all posts
Showing posts with label machines. Show all posts

Friday, March 30, 2012

Receiving Error 26 when trying to connect to DB...Some Machines

Good Day,

We have a recently developed (and in testing) VB .Net application which attaches to a specific SQL2005 DB. The issue is that when installed (or run in DEBUG mode) on the developer box it successfully connects to the appropriate db locally and to the live server. When installed on a test box (several of them) we receive error - 26 Error locating Server/Instance Specified.

The SQL Server instance is set up for remote connections and works for other dbs.

All of the boxes are running XP Pro, with all SPs applied.

Any thoughts on what may be occuring would be greatly appreciated.

This might help:
"Connection error occurs when the Database Engine service account password expires

The

following error occurs when you connect to a report server, and the

service account password has expired for the SQL Server Database Engine

instance that hosts the report server database: "The report server

cannot open a connection to the report server database. A connection to

the database is required for all requests and processing.

(rsReportServerDatabaseUnavailable)."

The error message includes

these additional statements: "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 Server Network

Interfaces, error: 26 - Error Locating Server/Instance Specified)."

To resolve this error, reset the password. For more information, see Changing Passwords and User Accounts."

http://msdn2.microsoft.com/en-us/library/ms156468.aspx

Also check out this kb:
http://support.microsoft.com/kb/905618

Friday, March 23, 2012

Rebuild SQL server 7 db

Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli
>> I can't use detach or attach sp from the new box.
You mean, you are getting some errors while trying to attach the databases?
If so, what are they?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli
|||Hi,
If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM and
User databases then you can do below:-
1. Install SQL Server 7 in the same folder as old installation
2. Apply the same service pack as old
3. Stop SQL Server service
4. COpy the new physical files to a new folder
5. Copy the physical files (MDF, NDF and LDF) from the old server to the
exact folders as old
6. Start the SQL Server service
7. Open enterprise manager and see if all the databases are ok.
Incase if this step fails then you need to:-
Restore the databases from last good backup.
Thanks
Hari
SQL Server MVP
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
> Our NT 4.0 server machine's motherboard burned out. After placed the hard
> disk drives in a new box, we got a video issue and disk I/O error.
> Therefore
> I installed SQL server 7 on a new Win2K server box. The hard disk drives
> on
> the NT server are fine and placed in the new box. I can't use detach or
> attach sp from the new box. How can I restore the db to the new box?
> Thanks,
> Eli
>
|||Hi Narayana & Hai,
Thank you so much for your replies. Because the db was not normally
detached, therefore I didn't know how to attach it to a new SQL serverl.
I'll try Hai's instructions to see how it works. Thanks again, really
apreciate it.
Eli
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ursSf8gkFHA.3828@.TK2MSFTNGP12.phx.gbl...
> Hi,
> If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM
and[vbcol=seagreen]
> User databases then you can do below:-
> 1. Install SQL Server 7 in the same folder as old installation
> 2. Apply the same service pack as old
> 3. Stop SQL Server service
> 4. COpy the new physical files to a new folder
> 5. Copy the physical files (MDF, NDF and LDF) from the old server to the
> exact folders as old
> 6. Start the SQL Server service
> 7. Open enterprise manager and see if all the databases are ok.
> Incase if this step fails then you need to:-
> Restore the databases from last good backup.
> Thanks
> Hari
> SQL Server MVP
>
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
hard
>

Monday, March 12, 2012

Reboot SQL Server 2000 server periodically ?

We currently reboot our Citrix and Application Server server/machines
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 2000
periodically ? If so how often ?
Our servers/machines are Windows 2003
ThanksWell Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server 2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks