Pleeeease help? I get an error when expanding the Tables object under linked servers in Enterprise Manager on a MSSQL2000 server.
I have a standard install of the Pervasive.SQL V8 data engine and DemoData db on my local PC. The SQL Server is also on my local PC.
I manage to create the Linked Server using the MSSQL Enterprise Manager. I used the following configuration:
Provider Name: Pervasive.SQL V8 OLE DB Provider
Product Name: Pervasive.SQL V8
Data source: DemoData
Provider string: <blank>
Location: workstation03
Catalog: <blank>
However when I try to expand the tables object under Linked Servers in the Enterprise manager I get the following error.
Error 7311: Could not obtain the schema rowset for the OLE DB provider 'UNKNOWN'. The provider supports the interface, but retuns a failure code when it is used. OLE DB error trace [OLE/DB Provider 'UNKNOWN' IDBSchemaRowset::GetRowset returned 0x80040155 ].
How would I fix this?
Thank you.moving to microsoft sql server forumsql
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Thursday, March 29, 2012
Monday, March 26, 2012
Error during installation of reporting services
Hi,
I've stuck with an error message and I can't sort it out. I am trying to
install a standard reporting service on a server separated from database
server.
Web server (report services): no domain
Databasebase server: a member of a domain.
I can install RS with domain authentication mode but I can't with SQL
authentication such as sa.
Errror message:
login failed for user '(null)'. reason: not associated with a trusted sql
server connection.
Anyone have an workaround for this error?
ThanksI found that using setup /i command lines and I did without any problem.
"Oliver" <dummy@.hotmail.com> wrote in message
news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've stuck with an error message and I can't sort it out. I am trying to
> install a standard reporting service on a server separated from database
> server.
> Web server (report services): no domain
> Databasebase server: a member of a domain.
> I can install RS with domain authentication mode but I can't with SQL
> authentication such as sa.
> Errror message:
> login failed for user '(null)'. reason: not associated with a trusted sql
> server connection.
> Anyone have an workaround for this error?
> Thanks
>|||Running setup with the /i command line did not have any impact on this issue
for me.
"Oliver" wrote:
> I found that using setup /i command lines and I did without any problem.
> "Oliver" <dummy@.hotmail.com> wrote in message
> news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I've stuck with an error message and I can't sort it out. I am trying to
> > install a standard reporting service on a server separated from database
> > server.
> > Web server (report services): no domain
> > Databasebase server: a member of a domain.
> >
> > I can install RS with domain authentication mode but I can't with SQL
> > authentication such as sa.
> >
> > Errror message:
> > login failed for user '(null)'. reason: not associated with a trusted sql
> > server connection.
> >
> > Anyone have an workaround for this error?
> >
> > Thanks
> >
> >
>
>
I've stuck with an error message and I can't sort it out. I am trying to
install a standard reporting service on a server separated from database
server.
Web server (report services): no domain
Databasebase server: a member of a domain.
I can install RS with domain authentication mode but I can't with SQL
authentication such as sa.
Errror message:
login failed for user '(null)'. reason: not associated with a trusted sql
server connection.
Anyone have an workaround for this error?
ThanksI found that using setup /i command lines and I did without any problem.
"Oliver" <dummy@.hotmail.com> wrote in message
news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've stuck with an error message and I can't sort it out. I am trying to
> install a standard reporting service on a server separated from database
> server.
> Web server (report services): no domain
> Databasebase server: a member of a domain.
> I can install RS with domain authentication mode but I can't with SQL
> authentication such as sa.
> Errror message:
> login failed for user '(null)'. reason: not associated with a trusted sql
> server connection.
> Anyone have an workaround for this error?
> Thanks
>|||Running setup with the /i command line did not have any impact on this issue
for me.
"Oliver" wrote:
> I found that using setup /i command lines and I did without any problem.
> "Oliver" <dummy@.hotmail.com> wrote in message
> news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I've stuck with an error message and I can't sort it out. I am trying to
> > install a standard reporting service on a server separated from database
> > server.
> > Web server (report services): no domain
> > Databasebase server: a member of a domain.
> >
> > I can install RS with domain authentication mode but I can't with SQL
> > authentication such as sa.
> >
> > Errror message:
> > login failed for user '(null)'. reason: not associated with a trusted sql
> > server connection.
> >
> > Anyone have an workaround for this error?
> >
> > Thanks
> >
> >
>
>
Error during installation
I was installing SQL Server 2005 Standard Edition on Windows 2000 server. During the prerequisites installation .NET 2.0 installed sucessfully but unable to install Microsoft SQL Native Client and produce an error.
Error occurred during installation:
Error 1619 installing Microsoft SQL Native Client. See log file for more detailed information. This installation package could not be opened. Varify that the package exists and that you can access it, or contact the application vendor to valify that this is a valid Windows Installer package.
Log File Errors:
=== Verbose logging started: 7/24/200616:04:11Build type: SHIP UNICODE 3.01.4000.2435Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (04:98) [16:04:11:359]: Resetting cached policy values
MSI (c) (04:98) [16:04:11:359]: Machine policy value 'Debug' is 0
MSI (c) (04:98) [16:04:11:359]: ******* RunEngine:
******* Product: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (c) (04:98) [16:04:11:359]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (04:98) [16:04:11:359]: Grabbed execution mutex.
MSI (c) (04:98) [16:04:11:437]: Cloaking enabled.
MSI (c) (04:98) [16:04:11:437]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (04:98) [16:04:11:468]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D0:C0) [16:04:11:515]: Grabbed execution mutex.
MSI (s) (D0:C8) [16:04:11:515]: Resetting cached policy values
MSI (s) (D0:C8) [16:04:11:515]: Machine policy value 'Debug' is 0
MSI (s) (D0:C8) [16:04:11:515]: ******* RunEngine:
******* Product: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (s) (D0:C8) [16:04:11:531]: Note: 1: 2203 2: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi 3: -2147287037
MSI (s) (D0:C8) [16:04:11:531]: MainEngineThread is returning 3
MSI (c) (04:98) [16:04:11:531]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.Counter after decrement: -1
MSI (c) (04:98) [16:04:11:531]: MainEngineThread is returning 3
=== Verbose logging stopped: 7/24/200616:04:11 ===
Any ideas. Please help....
Thanks.
Zafar.
Zafar, if you're attempting to install SQL Server 2005 onto Windows Server 2000 via a network share it will not work. You either have to put the CD/DVD directly into the server's reader drive or copy the files from the network share to the local hard drive of the server to perform the installation.sqlThursday, March 22, 2012
Error doing manual backup
I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!
Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!
Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
Error doing manual backup
I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Managemen
t
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
>
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Managemen
t
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
>
Error doing manual backup
I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
> > I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> > get an error trying to backup to a local drive:
> >
> > Cannot verify the existence of the backup file location.
> >
> > I read how this usually refers to backing up to a network share or
> > something, but this is a local drive. I tried it logged in to the Management
> > Studio as trusted and SQL authentication.
> >
> > Any ideas? Thanks!
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
> > I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> > get an error trying to backup to a local drive:
> >
> > Cannot verify the existence of the backup file location.
> >
> > I read how this usually refers to backing up to a network share or
> > something, but this is a local drive. I tried it logged in to the Management
> > Studio as trusted and SQL authentication.
> >
> > Any ideas? Thanks!
Wednesday, March 21, 2012
Error Data bases not compatible, Installation Reporting services
Hi,
I install Report services (standard, developer, enterprise edition) on sql
server 2000 personal edition, and windows 2003 server enterprise, during the
installation, when creating the data base sends the following message of
error "This version of the data base of the Reporting services is not
compatible with the version of SQL server 2000"
all the scene this in Spanish language.
I do not understand because, help me please.
excuse I do not speak ingles, thanksYou are posting the same problem multiple times. The answer will be the
same. Personal edition will not work. See my other post which has links to
the MS website that documents this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Arturo Alegria Palacios" <Arturo Alegria
Palacios@.discussions.microsoft.com> wrote in message
news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> Hi,
> I install Report services (standard, developer, enterprise edition) on sql
> server 2000 personal edition, and windows 2003 server enterprise, during
> the
> installation, when creating the data base sends the following message of
> error "This version of the data base of the Reporting services is not
> compatible with the version of SQL server 2000"
> all the scene this in Spanish language.
> I do not understand because, help me please.
> excuse I do not speak ingles, thanks|||Thanks bruce, I am going to verify the documentation of website, will verify
the scene where this executing itself now
"Bruce L-C [MVP]" wrote:
> You are posting the same problem multiple times. The answer will be the
> same. Personal edition will not work. See my other post which has links to
> the MS website that documents this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Arturo Alegria Palacios" <Arturo Alegria
> Palacios@.discussions.microsoft.com> wrote in message
> news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> > Hi,
> > I install Report services (standard, developer, enterprise edition) on sql
> > server 2000 personal edition, and windows 2003 server enterprise, during
> > the
> > installation, when creating the data base sends the following message of
> > error "This version of the data base of the Reporting services is not
> > compatible with the version of SQL server 2000"
> >
> > all the scene this in Spanish language.
> >
> > I do not understand because, help me please.
> >
> > excuse I do not speak ingles, thanks
>
>
I install Report services (standard, developer, enterprise edition) on sql
server 2000 personal edition, and windows 2003 server enterprise, during the
installation, when creating the data base sends the following message of
error "This version of the data base of the Reporting services is not
compatible with the version of SQL server 2000"
all the scene this in Spanish language.
I do not understand because, help me please.
excuse I do not speak ingles, thanksYou are posting the same problem multiple times. The answer will be the
same. Personal edition will not work. See my other post which has links to
the MS website that documents this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Arturo Alegria Palacios" <Arturo Alegria
Palacios@.discussions.microsoft.com> wrote in message
news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> Hi,
> I install Report services (standard, developer, enterprise edition) on sql
> server 2000 personal edition, and windows 2003 server enterprise, during
> the
> installation, when creating the data base sends the following message of
> error "This version of the data base of the Reporting services is not
> compatible with the version of SQL server 2000"
> all the scene this in Spanish language.
> I do not understand because, help me please.
> excuse I do not speak ingles, thanks|||Thanks bruce, I am going to verify the documentation of website, will verify
the scene where this executing itself now
"Bruce L-C [MVP]" wrote:
> You are posting the same problem multiple times. The answer will be the
> same. Personal edition will not work. See my other post which has links to
> the MS website that documents this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Arturo Alegria Palacios" <Arturo Alegria
> Palacios@.discussions.microsoft.com> wrote in message
> news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> > Hi,
> > I install Report services (standard, developer, enterprise edition) on sql
> > server 2000 personal edition, and windows 2003 server enterprise, during
> > the
> > installation, when creating the data base sends the following message of
> > error "This version of the data base of the Reporting services is not
> > compatible with the version of SQL server 2000"
> >
> > all the scene this in Spanish language.
> >
> > I do not understand because, help me please.
> >
> > excuse I do not speak ingles, thanks
>
>
Error Creating Maintenance Plan
I have a new installation of SQL 2005 x64 SP 1 Standard Edition installed on
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so
I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/...&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/...&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so
I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/...&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/...&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark
Error Creating Maintenance Plan
I have a new installation of SQL 2005 x64 SP 1 Standard Edition installed on
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark
Friday, March 9, 2012
Error connecting to SQL server
Hi,
We have a Windows 2000 terminal server with service pack 4 loaded.This has siebel application 7.8.2 .
We have another Windows 2003 standard edition server with service pack 1. This has SQL 2000 server with Service pack 4 installed.
When trying to connect to the sql server through odbc , i get an error
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
OK
-I am able to ping the server and viceversa.
Please let me know how to resolve this problem
Then you either have a different port than 1433 (you will have to specify the portnumber after the instance / servername with the syntax --> default instance Servername,Portnumber ; Servername\InstanceName,Portnumber for named instances). Do you have a firewall installed ? Then you will have to check if the appropiate port for SQL are enabled.HTH, jens Suessmeyer.
http://www.sqlserver2005.de|||
Please follow the instruction and give us more details:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
|||
Hi
The port is configured to 1433
There is no firewall installed
does it happen due to ODBC version.?
|||the issue is most likely that you are using terminal server and the odbc is a user odbc, and not a system odbc. if system odbc has not been created for the connection that is having the issue, create it.
ping uses icmp, and not always best test. test the odbc, recreate it if necessary. to check the 1433 port, open telnet client and type in telnet:1433; if it opens, the port is open, otherwise you know it's closed.
also check that the db is using the 1433 port (could have been configured to use alternate).
btw- i don't think siebel 7.8.2 is supported on 2000 server
Error connecting to SQL server
Hi,
We have a Windows 2000 terminal server with service pack 4 loaded.This has siebel application 7.8.2 .
We have another Windows 2003 standard edition server with service pack 1. This has SQL 2000 server with Service pack 4 installed.
When trying to connect to the sql server through odbc , i get an error
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
OK
-I am able to ping the server and viceversa.
Please let me know how to resolve this problem
Then you either have a different port than 1433 (you will have to specify the portnumber after the instance / servername with the syntax --> default instance Servername,Portnumber ; Servername\InstanceName,Portnumber for named instances). Do you have a firewall installed ? Then you will have to check if the appropiate port for SQL are enabled.HTH, jens Suessmeyer.
http://www.sqlserver2005.de
|||
Please follow the instruction and give us more details:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
Hi
The port is configured to 1433
There is no firewall installed
does it happen due to ODBC version.?
|||the issue is most likely that you are using terminal server and the odbc is a user odbc, and not a system odbc. if system odbc has not been created for the connection that is having the issue, create it.
ping uses icmp, and not always best test. test the odbc, recreate it if necessary. to check the 1433 port, open telnet client and type in telnet:1433; if it opens, the port is open, otherwise you know it's closed.
also check that the db is using the 1433 port (could have been configured to use alternate).
btw- i don't think siebel 7.8.2 is supported on 2000 server
Subscribe to:
Posts (Atom)