Showing posts with label install. Show all posts
Showing posts with label install. Show all posts

Saturday, February 25, 2012

"Microsoft SQL Servers" not showing in Computer Management.

Hi there,

Got a small tech support problem. We gave our manual writer an installer
that should install SQL Server (MSDE) and our software. Over the phone I've
managed to ascertain that SQL Server is installed (it is running as a
service, along with SQL Server Agent), but it does not show up in "Computer
Management -> Services and Applications". I need to set the permissions for
this user (over the phone!) in order to get our test software to work and
yet it does not show here. What am I doing wrong? (and/or why would the
MSDE instance not show up here?).

Thanks,

RobinI sorted it :)

"Robin Tucker" <idontwanttobespammedanymore@.reallyidont.com> wrote in
message news:cq6ak0$fkg$1$8300dec7@.news.demon.co.uk...
> Hi there,
>
> Got a small tech support problem. We gave our manual writer an installer
> that should install SQL Server (MSDE) and our software. Over the phone
> I've managed to ascertain that SQL Server is installed (it is running as a
> service, along with SQL Server Agent), but it does not show up in
> "Computer Management -> Services and Applications". I need to set the
> permissions for this user (over the phone!) in order to get our test
> software to work and yet it does not show here. What am I doing wrong?
> (and/or why would the MSDE instance not show up here?).
> Thanks,
>
> Robin

"Local" Server

All:
I was using a 120 day eval of SQL Server, and then purchased the developers
edition. During the install....and don't ask me exactly how I did it, I
ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
managed to remove the TVB and now have no "local" server, so to speak. I
can't find the setting to rectify this, although the database works
OK...but when using connection strings, I can't use localhost in the code,
I have to use the actual name, fortunately I can still use it in the URL.
This is probably easy to rectify if one knows where to look or what to do,
and I fear this may cause a problem bigger than the minor annoyance it is
now down the line. (Plus I only have a few apps set up , many more to come)
Advice greatly appreciated, thanks in advance.
Tom BThe only way to rectify this is to uninstall the named instance and
reinstall as a default instance. You cannot rename a SQL Server named
instance. If you have databases you want to keep then you can back them up
or detach them before uninstalling and then restore or attach them to your
default instance (that will have the same name as the server)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Bernsen" <t.bernsen@.worldnet.att.net> wrote in message
news:%23VGj0hN9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> All:
> I was using a 120 day eval of SQL Server, and then purchased the
developers
> edition. During the install....and don't ask me exactly how I did it, I
> ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
> managed to remove the TVB and now have no "local" server, so to speak. I
> can't find the setting to rectify this, although the database works
> OK...but when using connection strings, I can't use localhost in the
code,
> I have to use the actual name, fortunately I can still use it in the URL.
> This is probably easy to rectify if one knows where to look or what to do,
> and I fear this may cause a problem bigger than the minor annoyance it is
> now down the line. (Plus I only have a few apps set up , many more to
come)
> Advice greatly appreciated, thanks in advance.
> Tom B
>

"Local" Server

All:
I was using a 120 day eval of SQL Server, and then purchased the developers
edition. During the install....and don't ask me exactly how I did it, I
ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
managed to remove the TVB and now have no "local" server, so to speak. I
can't find the setting to rectify this, although the database works
OK...but when using connection strings, I can't use localhost in the code,
I have to use the actual name, fortunately I can still use it in the URL.
This is probably easy to rectify if one knows where to look or what to do,
and I fear this may cause a problem bigger than the minor annoyance it is
now down the line. (Plus I only have a few apps set up , many more to come)
Advice greatly appreciated, thanks in advance.
Tom BThe only way to rectify this is to uninstall the named instance and
reinstall as a default instance. You cannot rename a SQL Server named
instance. If you have databases you want to keep then you can back them up
or detach them before uninstalling and then restore or attach them to your
default instance (that will have the same name as the server)
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Bernsen" <t.bernsen@.worldnet.att.net> wrote in message
news:%23VGj0hN9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> All:
> I was using a 120 day eval of SQL Server, and then purchased the
developers
> edition. During the install....and don't ask me exactly how I did it, I
> ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
> managed to remove the TVB and now have no "local" server, so to speak. I
> can't find the setting to rectify this, although the database works
> OK...but when using connection strings, I can't use localhost in the
code,
> I have to use the actual name, fortunately I can still use it in the URL.
> This is probably easy to rectify if one knows where to look or what to do,
> and I fear this may cause a problem bigger than the minor annoyance it is
> now down the line. (Plus I only have a few apps set up , many more to
come)
> Advice greatly appreciated, thanks in advance.
> Tom B
>

Monday, February 13, 2012

"Error!" msg during "setup support files" installation

Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
"Error!" msg during "setup support files" installation.
Unable to install Reporting Services. Found a couple of users experiencing
the same problem, but no solution :( Any ideas?
/ChrisFirst, check the error log in Event Viewer and see if you can find any
EventID number for your error. That can pinpoint what the error really is.
If it's error 25619, then check if the DTC service is running? Go check in
services.msc for "Distributed Transaction Coordinator".
Even if it says "started", it might not be. I've had some troubles with
installing RS, and the DTC was the culprit.
It's been discussed in this thread:
http://groups.google.com/groups?hl=en&lr=&threadm=89FD4D17-1F6A-4BCF-A15E-CF098C5A68D7%40microsoft.com&rnum=1
In this thread, Pitroda asks about a password for Network Service. Just
leave the password blank, at least that worked for me.
Kaisa M. Lindahl
"Chris Leaf" <ChrisLeaf@.discussions.microsoft.com> wrote in message
news:E6F567CB-08C9-4B49-8544-9DB32826CC09@.microsoft.com...
> Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
> "Error!" msg during "setup support files" installation.
> Unable to install Reporting Services. Found a couple of users experiencing
> the same problem, but no solution :( Any ideas?
> /Chris|||Event log says:
"Product: Microsoft SQL Server 2000 Reporting Services Enterprise Edition --
Please install SQL Server by running setup.exe."
and
"Product: Microsoft SQL Server 2000 Reporting Services Enterprise Edition --
Installation failed."
install log ends with:
<Func Name='SqlSetupFilesComp::Install'>
<Func Name='BootstrapPackageLogic'>
<Func Name='InstallBootstrapPackage'>
/I "D:\Setup\bootmsi.dat" REBOOT="ReallySuppress"
ADDLOCAL="BootstrapFiles,WatsonFiles,ParsFiles1033,HelpFiles1028,HelpFiles1031,HelpFiles1033,HelpFiles1036,HelpFiles1040,HelpFiles1041,HelpFiles1042,HelpFiles2052,HelpFiles3082,WatsonFiles1033" /qn
<EndFunc Name='InstallBootstrapPackage' Return='1603' GetLastError='183'>
<EndFunc Name='BootstrapPackageLogic' Return='1603' GetLastError='183'>
SqlSetupFilesComp BootstrapPackageLogic() failed : (1603)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:565}
SCU_SetupMgr::svc() caught exception: SqlSetupFilesComp
BootstrapPackageLogic() failed : (1603)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:565}. SetupMgr:
state=ERROR, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0,
custom_props={AutoStart=true
HandleReboots=false
ModuleDir=D:
QuietMode=false
Unattended=false
WorkDir=D:
}} {n:\rosetta\dev\src\everettsetup\sqlcu\dll\scusetupmgr.cpp:428}
ScuProgressDlg::SetupFinished()
ScuProgressDlg::DialogProc() installation done... waiting for setup mgr
<EndFunc Name='UpdateComponents' Return='1602' GetLastError='0'>
DTC is running..
Thanks for your response.
"Kaisa M. Lindahl" wrote:
> First, check the error log in Event Viewer and see if you can find any
> EventID number for your error. That can pinpoint what the error really is.
> If it's error 25619, then check if the DTC service is running? Go check in
> services.msc for "Distributed Transaction Coordinator".
> Even if it says "started", it might not be. I've had some troubles with
> installing RS, and the DTC was the culprit.
> It's been discussed in this thread:
> http://groups.google.com/groups?hl=en&lr=&threadm=89FD4D17-1F6A-4BCF-A15E-CF098C5A68D7%40microsoft.com&rnum=1
> In this thread, Pitroda asks about a password for Network Service. Just
> leave the password blank, at least that worked for me.
> Kaisa M. Lindahl
> "Chris Leaf" <ChrisLeaf@.discussions.microsoft.com> wrote in message
> news:E6F567CB-08C9-4B49-8544-9DB32826CC09@.microsoft.com...
> > Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
> >
> > "Error!" msg during "setup support files" installation.
> > Unable to install Reporting Services. Found a couple of users experiencing
> > the same problem, but no solution :( Any ideas?
> >
> > /Chris
>
>

"downgrade" edition ?

Hi
I save SQLServer 7.0 enterprise edition installed on NT
4.0 PDC.
And now i want to install SQLServer 2000 standard edition
and upgrade default instance. When i run SQLServer 2000
setup, the option "Upgrade..." is not available.
I think it happens because different version: enterprise
and standart (or not ?)
How i can "downgrade" SQLServer edition ?
Or i should backup all 7 databases, install SQLServer 2000
and restore all databases from backup,include master (to
preserve logins)?I can point you in the direction of a good article on this subject :-
http://www.sqlteam.com/item.asp?ItemID=9066
--
HTH
Ryan Waight, MCDBA, MCSE
"Slava Melnikov" <melnikov@.pochta.ru> wrote in message
news:0a0201c38eed$a99fee90$a301280a@.phx.gbl...
> Hi
> I save SQLServer 7.0 enterprise edition installed on NT
> 4.0 PDC.
> And now i want to install SQLServer 2000 standard edition
> and upgrade default instance. When i run SQLServer 2000
> setup, the option "Upgrade..." is not available.
> I think it happens because different version: enterprise
> and standart (or not ?)
> How i can "downgrade" SQLServer edition ?
> Or i should backup all 7 databases, install SQLServer 2000
> and restore all databases from backup,include master (to
> preserve logins)?

Friday, January 27, 2012

! PLEASE HELP !! Collation selection on install

Hi, I need to change the collation when I install SQL Express 2005 to SQL_LATIN1_GENERAL_CP1_CI_AS but the drop down on setup only allows

LATIN1_GENERAL.

How do I get the correct collation to appear?

Thanks for any help/tips

hi,

as you can see in http://msdn2.microsoft.com/en-us/library/ms144250.aspx, SQL collations are for compatibility with older settings and are not directly listed (as you want them) in the installation wizard.... you can "only" choose a Windows collation, that lists all the variations of each particular collation, or SQL collation, that you have to "customize" to fit your needs.. so, for SQL_LATIN1_GENERAL_CP1_CI_AS you have to choose Dictionary order, case-insensitive, 1252 character set (or alternate locale to fit your needs)..

regards

|||Kool....thanks a million that did the trick ;-)