Running a Job from ASP

I have a post similar to this is the Getting Started thread but haven't had any responses so I'm going to ask an updated version of my question. What I need to do is run a job after a user clicks a button in my ASP page. I know I can use oDBConnection.pStoredProc to run a stored procedure, but is there a similar command I can use to run the job? Any help will be appreciated. Thanks
Tim Conlan
InternTry this:
http://www.sqlteam.com/item.asp?ItemID=19595
|||Darrell, that's pretty much exactly what I was looking for. Thanks for the heads.
Tim Conlan|||

Actually, if you have the time I have a second question about puting together the DTS package. I get the fact that I can write the Stored Proc to dynamically create the job that will run the DTS package on the remote server, at least I think that's what I understand, but I want to make sure that I understand. So, the St Proc accepts a @.variable from my ASP page. The St Proc then appends the @.variable to the DTSrun command line script. So, how do I reference the @.variable when I put together the DTS package? I'm building it in Enterprise Manager and I see the field that says "Parameters:", do I just put @.variable in that field or do I need to put something else in there to get the package to pass the @.variable to the .BAT file that I will run with the DTS package?
If I've confused you or didn't provide enough information I'd be happy to clarify. Thanks
Tim Conlan
Intern (but getting better at this all the time)

|||I think you just put @.variable in there.

Running 64 Bit instance and 32 bit instance on Same Server

We are using an OEM ODBC connector that, to date, only works with the 32 bit
version of SQL 2005. My production server is a 64 bit version so I am still
maintaing the old server with the 32 bit for this ONE connectivity
requirement. The ODBC / OLEDB connector is used for a LINKED server to a
PROGRESS database.
Can I install the 32 BIT version of SQL on the same (64bit version of)
Windows Server 2003, and should I expect that the OEM ODBC driver would
function in the 32 bit instance as it does on the 32 bit Server?
--
Thanks~
JimDear Jim,
Thank you for posting here.
From your description, I understand that:
Your current ODBC connector is based on SQL Server 2005 32 bit; however
production server is a 64 bit version and you would like to know whether we
can install SQL Server 32bit on the 64 bit Windows Server 2003 and run both
64 bit and 32 bit SQL instances on it.
If I have misunderstood about your concern, feel free to let me know.
Windows Server 2003 64 bit Edition fully supports SQL Server 2005 32 bit
Editions. You can refer to the section "Operating System Requirements
(32-Bit)" of this article "Hardware and Software Requirements for
Installing SQL Server 2005":
http://msdn2.microsoft.com/en-us/library/ms143506.aspx
So, we are able to install the 32bit instance on the same 64 bit server. In
addition, we need to use "odbcad32.exe" on the 64bit system to configure
DSN for 32 bit driver. In most cases, the OEM ODBC connector should work in
this scenario. We can also contact the manufacturer of this ODBC connector
to confirm this.
If anything is unclear in my post, please don't hesitate to let me know.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Running 64 Bit instance and 32 bit instance on Same Server
| thread-index: Acgb8YBLwppW8NlwQ/C3lA9P6QDrsQ==| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?QmlnSmltQ2FzaA==?= <Bigjimcash@.noemail.noemail>
| Subject: Running 64 Bit instance and 32 bit instance on Same Server
| Date: Wed, 31 Oct 2007 12:09:03 -0700
| Lines: 12
| Message-ID: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29189
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| We are using an OEM ODBC connector that, to date, only works with the 32
bit
| version of SQL 2005. My production server is a 64 bit version so I am
still
| maintaing the old server with the 32 bit for this ONE connectivity
| requirement. The ODBC / OLEDB connector is used for a LINKED server to a
| PROGRESS database.
|
| Can I install the 32 BIT version of SQL on the same (64bit version of)
| Windows Server 2003, and should I expect that the OEM ODBC driver would
| function in the 32 bit instance as it does on the 32 bit Server?
| --
| Thanks~
| Jim
||||Dear Jim,
We wanted to see if the information provided was helpful. Please keep us
posted on your progress and let us know if you have any additional
questions or concerns.
We are looking forward to your response.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 54548849
| References: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Thu, 01 Nov 2007 06:25:20 GMT
| Subject: RE: Running 64 Bit instance and 32 bit instance on Same Server
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <7#wKAAFHIHA.4508@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 82
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29229
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for posting here.
|
| From your description, I understand that:
|
| Your current ODBC connector is based on SQL Server 2005 32 bit; however
| production server is a 64 bit version and you would like to know whether
we
| can install SQL Server 32bit on the 64 bit Windows Server 2003 and run
both
| 64 bit and 32 bit SQL instances on it.
|
| If I have misunderstood about your concern, feel free to let me know.
|
| Windows Server 2003 64 bit Edition fully supports SQL Server 2005 32 bit
| Editions. You can refer to the section "Operating System Requirements
| (32-Bit)" of this article "Hardware and Software Requirements for
| Installing SQL Server 2005":
| http://msdn2.microsoft.com/en-us/library/ms143506.aspx
|
| So, we are able to install the 32bit instance on the same 64 bit server.
In
| addition, we need to use "odbcad32.exe" on the 64bit system to configure
| DSN for 32 bit driver. In most cases, the OEM ODBC connector should work
in
| this scenario. We can also contact the manufacturer of this ODBC
connector
| to confirm this.
|
| If anything is unclear in my post, please don't hesitate to let me know.
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu
| MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
| --
| | Thread-Topic: Running 64 Bit instance and 32 bit instance on Same Server
| | thread-index: Acgb8YBLwppW8NlwQ/C3lA9P6QDrsQ==| | X-WBNR-Posting-Host: 207.46.19.168
| | From: =?Utf-8?B?QmlnSmltQ2FzaA==?= <Bigjimcash@.noemail.noemail>
| | Subject: Running 64 Bit instance and 32 bit instance on Same Server
| | Date: Wed, 31 Oct 2007 12:09:03 -0700
| | Lines: 12
| | Message-ID: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="Utf-8"
| | Content-Transfer-Encoding: 7bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | Content-Class: urn:content-classes:message
| | Importance: normal
| | Priority: normal
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| | Newsgroups: microsoft.public.sqlserver.server
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29189
| | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | We are using an OEM ODBC connector that, to date, only works with the
32
| bit
| | version of SQL 2005. My production server is a 64 bit version so I am
| still
| | maintaing the old server with the 32 bit for this ONE connectivity
| | requirement. The ODBC / OLEDB connector is used for a LINKED server to
a
| | PROGRESS database.
| |
| | Can I install the 32 BIT version of SQL on the same (64bit version of)
| | Windows Server 2003, and should I expect that the OEM ODBC driver would
| | function in the 32 bit instance as it does on the 32 bit Server?
| | --
| | Thanks~
| | Jim
| |
|
|

running 32bit standard edition on 64bit hardware?

I just found out that the hardware that came uses 64bit AMD. But the
Windows Server 2003 license is for Standard Edition; a 32bit version.
What kind of performance hit would I take if I ran the Standard Edition
on the 64bit hardware?
Thanks,
Mark.None.
If you install the 64 bit OS, your executables will be a bit larger and
yoyu'll use a bit more memory. But then, you can install way more memory :)
"Mark" <murkynow50@.yahoo.com> wrote in message
news:OreRLT8%23HHA.4184@.TK2MSFTNGP05.phx.gbl...
>I just found out that the hardware that came uses 64bit AMD. But the
>Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition on
> the 64bit hardware?
> Thanks,
> Mark.|||Mark wrote:
> I just found out that the hardware that came uses 64bit AMD. But the
> Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition
> on the 64bit hardware?
> Thanks,
> Mark.
Sorry about this posting. I meant to post it in the windows section.
Mark.

RTM install order with VS2005 ?

With the RTM versions of SQL 2005 and VS 2005, does it matter which order they are installed in, or now that they are all on the same version of the .NET framework, does installation order no longer matter ?

Also, are there any issues/gotchas with installing SQL 2005 Developer edition and SQL 2005 Express from the VS2005 RTM on the same machine ?

During the betas, there were all sorts of hoops you had to jump through, and do things in certain orders, but with RTM will the standard installs of SQL 2005 Developer, VS 2005 and SQL 2005 Express all work regardless of install order ?

Thanks,
Andy Mackie.Order shouldn't matter at all any more, nor should there be any gotchas with the SxS scenario you describe.|||It shouldn't matter, but I stuck with the MS recommendations of VS2005 first - using a custom install so it did not install SQL Express - then SQL 2005 all up.
No problems at all
HTH,
Richard
|||Hello Richard,
I was wondering if you or anyone has had success installing VS2005 first, including Express Edition of SQL Server, and then installing the whole SQL Server on top of that. It seems to have problems installing the management tools - notably SQL Server Managemetn Studio - when I do it in that order.

What I'm really asking is if it's possible to install SSMS if you already have SQL Express 2005 installed?|||

Hi Robert,

I installed VS2005, but explicitly excluded SQL Express edition. I then did a full install of SQL Server 2005.

In theory I don't see why you should not be able to install JUST the client tools onto your machine, using the SQL server disks. I did an install a while back with no client tools on the server, then realised I needed to add them in. I was able to add them in OK.

I have a feeling that VS2005 puts it's own set of client tools on when you put Enterprise edition on, which may give you problems. Presumably you can Uninstall the EE components using the VS2005 disks, then put on SQL server?

Hope this helps,

Richard

RTM install order with VS2005 ?

With the RTM versions of SQL 2005 and VS 2005, does it matter which order they are installed in, or now that they are all on the same version of the .NET framework, does installation order no longer matter ?

Also, are there any issues/gotchas with installing SQL 2005 Developer edition and SQL 2005 Express from the VS2005 RTM on the same machine ?

During the betas, there were all sorts of hoops you had to jump through, and do things in certain orders, but with RTM will the standard installs of SQL 2005 Developer, VS 2005 and SQL 2005 Express all work regardless of install order ?

Thanks,
Andy Mackie.Order shouldn't matter at all any more, nor should there be any gotchas with the SxS scenario you describe.|||It shouldn't matter, but I stuck with the MS recommendations of VS2005 first - using a custom install so it did not install SQL Express - then SQL 2005 all up.
No problems at all
HTH,
Richard
|||Hello Richard,
I was wondering if you or anyone has had success installing VS2005 first, including Express Edition of SQL Server, and then installing the whole SQL Server on top of that. It seems to have problems installing the management tools - notably SQL Server Managemetn Studio - when I do it in that order.

What I'm really asking is if it's possible to install SSMS if you already have SQL Express 2005 installed?|||

Hi Robert,

I installed VS2005, but explicitly excluded SQL Express edition. I then did a full install of SQL Server 2005.

In theory I don't see why you should not be able to install JUST the client tools onto your machine, using the SQL server disks. I did an install a while back with no client tools on the server, then realised I needed to add them in. I was able to add them in OK.

I have a feeling that VS2005 puts it's own set of client tools on when you put Enterprise edition on, which may give you problems. Presumably you can Uninstall the EE components using the VS2005 disks, then put on SQL server?

Hope this helps,

Richard

RTM install order with VS2005 ?

With the RTM versions of SQL 2005 and VS 2005, does it matter which order they are installed in, or now that they are all on the same version of the .NET framework, does installation order no longer matter ?

Also, are there any issues/gotchas with installing SQL 2005 Developer edition and SQL 2005 Express from the VS2005 RTM on the same machine ?

During the betas, there were all sorts of hoops you had to jump through, and do things in certain orders, but with RTM will the standard installs of SQL 2005 Developer, VS 2005 and SQL 2005 Express all work regardless of install order ?

Thanks,
Andy Mackie.Order shouldn't matter at all any more, nor should there be any gotchas with the SxS scenario you describe.|||It shouldn't matter, but I stuck with the MS recommendations of VS2005 first - using a custom install so it did not install SQL Express - then SQL 2005 all up.
No problems at all
HTH,
Richard
|||Hello Richard,
I was wondering if you or anyone has had success installing VS2005 first, including Express Edition of SQL Server, and then installing the whole SQL Server on top of that. It seems to have problems installing the management tools - notably SQL Server Managemetn Studio - when I do it in that order.

What I'm really asking is if it's possible to install SSMS if you already have SQL Express 2005 installed?|||

Hi Robert,

I installed VS2005, but explicitly excluded SQL Express edition. I then did a full install of SQL Server 2005.

In theory I don't see why you should not be able to install JUST the client tools onto your machine, using the SQL server disks. I did an install a while back with no client tools on the server, then realised I needed to add them in. I was able to add them in OK.

I have a feeling that VS2005 puts it's own set of client tools on when you put Enterprise edition on, which may give you problems. Presumably you can Uninstall the EE components using the VS2005 disks, then put on SQL server?

Hope this helps,

Richard

RSS Verifying DB version while upgrade

In Reporting Server2005 Configuration, while verifying database version and
trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does not
match your reporting server installation. you must upgrade your reporting
services database.
Please help, can not move forward.
Regards...Piku.This is a multi-part message in MIME format.
--=_NextPart_000_0047_01C6DC0C.4F605770
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
By the error message, it seems you're trying to install the RS 2005 =database to a database instance running SQL Server 2000. This seems to =be possible, but you have to do things differently during setup. This =article might help you in the right direction:
Using SQL 2000 for SSRS 2005 metadata storage
When setting up SQL Server Reporting Services 2005, can you use SQL 2000 =as the host for the reportserver database? Yes, you can (with an obvious =caveat in one scenario).

https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
Kaisa M. Lindahl Lervik
"Piku" <Piku@.discussions.microsoft.com> wrote in message =news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> In Reporting Server2005 Configuration, while verifying database =version and > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 =does not > match your reporting server installation. you must upgrade your =reporting > services database.
> > Please help, can not move forward.
> > Regards...Piku.
--=_NextPart_000_0047_01C6DC0C.4F605770
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

By the error message, it seems you're =trying to install the RS 2005 database to a database instance running SQL Server =2000. This seems to be possible, but you have to do things differently during =setup. This article might help you in the right direction:
Using SQL 2000 for SSRS 2005 =metadata storage
When setting up SQL Server Reporting Services 2005, can you =use SQL 2000 as the host for the reportserver database? Yes, you can (with an =obvious caveat in one scenario).
=https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.a=spx
Kaisa M. Lindahl Lervik
"Piku" wrote in message news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...> =In Reporting Server2005 Configuration, while verifying database version and > =trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does =not > match your reporting server installation. you must upgrade your =reporting > services database.> > Please help, can =not move forward.> > Regards...Piku.

---

--=_NextPart_000_0047_01C6DC0C.4F605770--|||I am installing rss 2005 on a SQL Server 2005 database, please help
"Kaisa M. Lindahl Lervik" wrote:
> By the error message, it seems you're trying to install the RS 2005 database to a database instance running SQL Server 2000. This seems to be possible, but you have to do things differently during setup. This article might help you in the right direction:
> Using SQL 2000 for SSRS 2005 metadata storage
>
> When setting up SQL Server Reporting Services 2005, can you use SQL 2000 as the host for the reportserver database? Yes, you can (with an obvious caveat in one scenario).
>
> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
>
> Kaisa M. Lindahl Lervik
>
> "Piku" <Piku@.discussions.microsoft.com> wrote in message news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> > In Reporting Server2005 Configuration, while verifying database version and
> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does not
> > match your reporting server installation. you must upgrade your reporting
> > services database.
> >
> > Please help, can not move forward.
> >
> > Regards...Piku|||OK, seems like someone else had the same problem a few weeks ago. His
problem and solution:
I had the same problem.
It was caused by that I had installed reporting services after I had run
SP1 on SQL Server 2005.
Solved it by runing SQL Server 2005 SP1 again.
Hope this helps!
(At the end of this thread:)
http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
Kaisa
"Piku" <Piku@.discussions.microsoft.com> wrote in message
news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
>I am installing rss 2005 on a SQL Server 2005 database, please help
> "Kaisa M. Lindahl Lervik" wrote:
>> By the error message, it seems you're trying to install the RS 2005
>> database to a database instance running SQL Server 2000. This seems to be
>> possible, but you have to do things differently during setup. This
>> article might help you in the right direction:
>> Using SQL 2000 for SSRS 2005 metadata storage
>>
>> When setting up SQL Server Reporting Services 2005, can you use SQL 2000
>> as the host for the reportserver database? Yes, you can (with an obvious
>> caveat in one scenario).
>>
>> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
>>
>> Kaisa M. Lindahl Lervik
>>
>> "Piku" <Piku@.discussions.microsoft.com> wrote in message
>> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
>> > In Reporting Server2005 Configuration, while verifying database version
>> > and
>> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does
>> > not
>> > match your reporting server installation. you must upgrade your
>> > reporting
>> > services database.
>> >
>> > Please help, can not move forward.
>> >
>> > Regards...Piku|||Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
install SQ1 again and see what happens, but have a doubt, SQL2005 instance
already has sp1 though. Thanks and appreciate your very quick response.
"Kaisa M. Lindahl Lervik" wrote:
> OK, seems like someone else had the same problem a few weeks ago. His
> problem and solution:
> I had the same problem.
> It was caused by that I had installed reporting services after I had run
> SP1 on SQL Server 2005.
> Solved it by runing SQL Server 2005 SP1 again.
>
> Hope this helps!
> (At the end of this thread:)
> http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
> Kaisa
> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
> >I am installing rss 2005 on a SQL Server 2005 database, please help
> >
> > "Kaisa M. Lindahl Lervik" wrote:
> >
> >> By the error message, it seems you're trying to install the RS 2005
> >> database to a database instance running SQL Server 2000. This seems to be
> >> possible, but you have to do things differently during setup. This
> >> article might help you in the right direction:
> >> Using SQL 2000 for SSRS 2005 metadata storage
> >>
> >>
> >> When setting up SQL Server Reporting Services 2005, can you use SQL 2000
> >> as the host for the reportserver database? Yes, you can (with an obvious
> >> caveat in one scenario).
> >>
> >>
> >>
> >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
> >>
> >>
> >> Kaisa M. Lindahl Lervik
> >>
> >>
> >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> >> > In Reporting Server2005 Configuration, while verifying database version
> >> > and
> >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does
> >> > not
> >> > match your reporting server installation. you must upgrade your
> >> > reporting
> >> > services database.
> >> >
> >> > Please help, can not move forward.
> >> >
> >> > Regards...Piku
>
>|||Actually my BUILD is 2153, which is one hotfix more than sp1
"Piku" wrote:
> Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
> install SQ1 again and see what happens, but have a doubt, SQL2005 instance
> already has sp1 though. Thanks and appreciate your very quick response.
> "Kaisa M. Lindahl Lervik" wrote:
> > OK, seems like someone else had the same problem a few weeks ago. His
> > problem and solution:
> >
> > I had the same problem.
> > It was caused by that I had installed reporting services after I had run
> > SP1 on SQL Server 2005.
> >
> > Solved it by runing SQL Server 2005 SP1 again.
> >
> >
> > Hope this helps!
> >
> > (At the end of this thread:)
> > http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
> >
> > Kaisa
> >
> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
> > >I am installing rss 2005 on a SQL Server 2005 database, please help
> > >
> > > "Kaisa M. Lindahl Lervik" wrote:
> > >
> > >> By the error message, it seems you're trying to install the RS 2005
> > >> database to a database instance running SQL Server 2000. This seems to be
> > >> possible, but you have to do things differently during setup. This
> > >> article might help you in the right direction:
> > >> Using SQL 2000 for SSRS 2005 metadata storage
> > >>
> > >>
> > >> When setting up SQL Server Reporting Services 2005, can you use SQL 2000
> > >> as the host for the reportserver database? Yes, you can (with an obvious
> > >> caveat in one scenario).
> > >>
> > >>
> > >>
> > >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
> > >>
> > >>
> > >> Kaisa M. Lindahl Lervik
> > >>
> > >>
> > >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> > >> > In Reporting Server2005 Configuration, while verifying database version
> > >> > and
> > >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40 does
> > >> > not
> > >> > match your reporting server installation. you must upgrade your
> > >> > reporting
> > >> > services database.
> > >> >
> > >> > Please help, can not move forward.
> > >> >
> > >> > Regards...Piku
> >
> >
> >|||OK, don't know what to do about that. :(
Kaisa
"Piku" <Piku@.discussions.microsoft.com> wrote in message
news:EFB33C14-C348-4457-A3FA-EEAD02FD932D@.microsoft.com...
> Actually my BUILD is 2153, which is one hotfix more than sp1
> "Piku" wrote:
>> Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
>> install SQ1 again and see what happens, but have a doubt, SQL2005
>> instance
>> already has sp1 though. Thanks and appreciate your very quick response.
>> "Kaisa M. Lindahl Lervik" wrote:
>> > OK, seems like someone else had the same problem a few weeks ago. His
>> > problem and solution:
>> >
>> > I had the same problem.
>> > It was caused by that I had installed reporting services after I had
>> > run
>> > SP1 on SQL Server 2005.
>> >
>> > Solved it by runing SQL Server 2005 SP1 again.
>> >
>> >
>> > Hope this helps!
>> >
>> > (At the end of this thread:)
>> > http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
>> >
>> > Kaisa
>> >
>> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
>> > news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
>> > >I am installing rss 2005 on a SQL Server 2005 database, please help
>> > >
>> > > "Kaisa M. Lindahl Lervik" wrote:
>> > >
>> > >> By the error message, it seems you're trying to install the RS 2005
>> > >> database to a database instance running SQL Server 2000. This seems
>> > >> to be
>> > >> possible, but you have to do things differently during setup. This
>> > >> article might help you in the right direction:
>> > >> Using SQL 2000 for SSRS 2005 metadata storage
>> > >>
>> > >>
>> > >> When setting up SQL Server Reporting Services 2005, can you use SQL
>> > >> 2000
>> > >> as the host for the reportserver database? Yes, you can (with an
>> > >> obvious
>> > >> caveat in one scenario).
>> > >>
>> > >>
>> > >>
>> > >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
>> > >>
>> > >>
>> > >> Kaisa M. Lindahl Lervik
>> > >>
>> > >>
>> > >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
>> > >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
>> > >> > In Reporting Server2005 Configuration, while verifying database
>> > >> > version
>> > >> > and
>> > >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40
>> > >> > does
>> > >> > not
>> > >> > match your reporting server installation. you must upgrade your
>> > >> > reporting
>> > >> > services database.
>> > >> >
>> > >> > Please help, can not move forward.
>> > >> >
>> > >> > Regards...Piku
>> >
>> >
>> >|||I reinstall the sp1 and it worked, doesn,t make any sense as I was already
having the higher build, anyway THANKS.
Now everything thing looks good BUT when I am trying to connect to the
report server by http://servername/reportserver OR
http://servername/reports getting Msg : " The feature: "Scale-out deployment"
is not supported in this edition of Reporting Services.
(rsOperationNotSupported) (rsRPCError"
I have installed One report server one sql server standard edition all on
one machine, then why am I getting this msg, I know only Dev and Entp Edition
supports Scale-Out deployment how to resolve it, please help.
Regards.
"Kaisa M. Lindahl Lervik" wrote:
> OK, don't know what to do about that. :(
> Kaisa
> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> news:EFB33C14-C348-4457-A3FA-EEAD02FD932D@.microsoft.com...
> > Actually my BUILD is 2153, which is one hotfix more than sp1
> >
> > "Piku" wrote:
> >
> >> Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
> >> install SQ1 again and see what happens, but have a doubt, SQL2005
> >> instance
> >> already has sp1 though. Thanks and appreciate your very quick response.
> >>
> >> "Kaisa M. Lindahl Lervik" wrote:
> >>
> >> > OK, seems like someone else had the same problem a few weeks ago. His
> >> > problem and solution:
> >> >
> >> > I had the same problem.
> >> > It was caused by that I had installed reporting services after I had
> >> > run
> >> > SP1 on SQL Server 2005.
> >> >
> >> > Solved it by runing SQL Server 2005 SP1 again.
> >> >
> >> >
> >> > Hope this helps!
> >> >
> >> > (At the end of this thread:)
> >> > http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
> >> >
> >> > Kaisa
> >> >
> >> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> >> > news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
> >> > >I am installing rss 2005 on a SQL Server 2005 database, please help
> >> > >
> >> > > "Kaisa M. Lindahl Lervik" wrote:
> >> > >
> >> > >> By the error message, it seems you're trying to install the RS 2005
> >> > >> database to a database instance running SQL Server 2000. This seems
> >> > >> to be
> >> > >> possible, but you have to do things differently during setup. This
> >> > >> article might help you in the right direction:
> >> > >> Using SQL 2000 for SSRS 2005 metadata storage
> >> > >>
> >> > >>
> >> > >> When setting up SQL Server Reporting Services 2005, can you use SQL
> >> > >> 2000
> >> > >> as the host for the reportserver database? Yes, you can (with an
> >> > >> obvious
> >> > >> caveat in one scenario).
> >> > >>
> >> > >>
> >> > >>
> >> > >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
> >> > >>
> >> > >>
> >> > >> Kaisa M. Lindahl Lervik
> >> > >>
> >> > >>
> >> > >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> >> > >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> >> > >> > In Reporting Server2005 Configuration, while verifying database
> >> > >> > version
> >> > >> > and
> >> > >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40
> >> > >> > does
> >> > >> > not
> >> > >> > match your reporting server installation. you must upgrade your
> >> > >> > reporting
> >> > >> > services database.
> >> > >> >
> >> > >> > Please help, can not move forward.
> >> > >> >
> >> > >> > Regards...Piku
> >> >
> >> >
> >> >
>
>|||Same problem here. I am trying to solve this issue since DAYS on the Italian
localized SQL 2005 Workgroup Edition of SQL 2005 on a SBS 2003 R2 PDC. Fresh
install, not upgrade.
I'm trying to install Reporting Services on the default db instance. The db
engine is now at 9.0.2153.
On the Report Server Configuration tool I'm on the "database setting" tab
(I'm translating everything from Italian, so labels could be literally
different).
I can connect to the server. I push the "New..." button. I create a db on
the default SQL instance. Credentials: Current user (running in the
Administrator context). DB Name: ReportServer. Language: either English or
Italian.
The DB gets built. I push the "Apply" button and a "Update the db"? message
appears. I click "OK". The status shows:
GREEN: Verification of the db edition: completed.
YELLOW TRIANGLE: Verification of the db version: "The DATABASE VERSION
C.0.8.40 does not match your reporting server installation. You must upgrade
your reporting services db".
YELLOW TRIANGLE: Creating the update script for the DB version C.0.8.40: No
update script available for this version of the db!
"Piku" wrote:
> I reinstall the sp1 and it worked, doesn,t make any sense as I was already
> having the higher build, anyway THANKS.
> Now everything thing looks good BUT when I am trying to connect to the
> report server by http://servername/reportserver OR
> http://servername/reports getting Msg : " The feature: "Scale-out deployment"
> is not supported in this edition of Reporting Services.
> (rsOperationNotSupported) (rsRPCError"
> I have installed One report server one sql server standard edition all on
> one machine, then why am I getting this msg, I know only Dev and Entp Edition
> supports Scale-Out deployment how to resolve it, please help.
> Regards.
> "Kaisa M. Lindahl Lervik" wrote:
> > OK, don't know what to do about that. :(
> >
> > Kaisa
> >
> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > news:EFB33C14-C348-4457-A3FA-EEAD02FD932D@.microsoft.com...
> > > Actually my BUILD is 2153, which is one hotfix more than sp1
> > >
> > > "Piku" wrote:
> > >
> > >> Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
> > >> install SQ1 again and see what happens, but have a doubt, SQL2005
> > >> instance
> > >> already has sp1 though. Thanks and appreciate your very quick response.
> > >>
> > >> "Kaisa M. Lindahl Lervik" wrote:
> > >>
> > >> > OK, seems like someone else had the same problem a few weeks ago. His
> > >> > problem and solution:
> > >> >
> > >> > I had the same problem.
> > >> > It was caused by that I had installed reporting services after I had
> > >> > run
> > >> > SP1 on SQL Server 2005.
> > >> >
> > >> > Solved it by runing SQL Server 2005 SP1 again.
> > >> >
> > >> >
> > >> > Hope this helps!
> > >> >
> > >> > (At the end of this thread:)
> > >> > http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
> > >> >
> > >> > Kaisa
> > >> >
> > >> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > >> > news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
> > >> > >I am installing rss 2005 on a SQL Server 2005 database, please help
> > >> > >
> > >> > > "Kaisa M. Lindahl Lervik" wrote:
> > >> > >
> > >> > >> By the error message, it seems you're trying to install the RS 2005
> > >> > >> database to a database instance running SQL Server 2000. This seems
> > >> > >> to be
> > >> > >> possible, but you have to do things differently during setup. This
> > >> > >> article might help you in the right direction:
> > >> > >> Using SQL 2000 for SSRS 2005 metadata storage
> > >> > >>
> > >> > >>
> > >> > >> When setting up SQL Server Reporting Services 2005, can you use SQL
> > >> > >> 2000
> > >> > >> as the host for the reportserver database? Yes, you can (with an
> > >> > >> obvious
> > >> > >> caveat in one scenario).
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
> > >> > >>
> > >> > >>
> > >> > >> Kaisa M. Lindahl Lervik
> > >> > >>
> > >> > >>
> > >> > >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > >> > >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> > >> > >> > In Reporting Server2005 Configuration, while verifying database
> > >> > >> > version
> > >> > >> > and
> > >> > >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40
> > >> > >> > does
> > >> > >> > not
> > >> > >> > match your reporting server installation. you must upgrade your
> > >> > >> > reporting
> > >> > >> > services database.
> > >> > >> >
> > >> > >> > Please help, can not move forward.
> > >> > >> >
> > >> > >> > Regards...Piku
> > >> >
> > >> >
> > >> >
> >
> >
> >|||I forgot to say: when I run the SQL 2005 SP1 install, it works for everything
except the reporting services. That gives "error" and stayis on SP0!
"davideC" wrote:
> Same problem here. I am trying to solve this issue since DAYS on the Italian
> localized SQL 2005 Workgroup Edition of SQL 2005 on a SBS 2003 R2 PDC. Fresh
> install, not upgrade.
> I'm trying to install Reporting Services on the default db instance. The db
> engine is now at 9.0.2153.
> On the Report Server Configuration tool I'm on the "database setting" tab
> (I'm translating everything from Italian, so labels could be literally
> different).
> I can connect to the server. I push the "New..." button. I create a db on
> the default SQL instance. Credentials: Current user (running in the
> Administrator context). DB Name: ReportServer. Language: either English or
> Italian.
> The DB gets built. I push the "Apply" button and a "Update the db"? message
> appears. I click "OK". The status shows:
> GREEN: Verification of the db edition: completed.
> YELLOW TRIANGLE: Verification of the db version: "The DATABASE VERSION
> C.0.8.40 does not match your reporting server installation. You must upgrade
> your reporting services db".
> YELLOW TRIANGLE: Creating the update script for the DB version C.0.8.40: No
> update script available for this version of the db!
>
> "Piku" wrote:
> > I reinstall the sp1 and it worked, doesn,t make any sense as I was already
> > having the higher build, anyway THANKS.
> >
> > Now everything thing looks good BUT when I am trying to connect to the
> > report server by http://servername/reportserver OR
> > http://servername/reports getting Msg : " The feature: "Scale-out deployment"
> > is not supported in this edition of Reporting Services.
> > (rsOperationNotSupported) (rsRPCError"
> >
> > I have installed One report server one sql server standard edition all on
> > one machine, then why am I getting this msg, I know only Dev and Entp Edition
> > supports Scale-Out deployment how to resolve it, please help.
> >
> > Regards.
> >
> > "Kaisa M. Lindahl Lervik" wrote:
> >
> > > OK, don't know what to do about that. :(
> > >
> > > Kaisa
> > >
> > > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > > news:EFB33C14-C348-4457-A3FA-EEAD02FD932D@.microsoft.com...
> > > > Actually my BUILD is 2153, which is one hotfix more than sp1
> > > >
> > > > "Piku" wrote:
> > > >
> > > >> Yes, My scenario is exactly same, sql2k5, sp1 and then rss2005...let me
> > > >> install SQ1 again and see what happens, but have a doubt, SQL2005
> > > >> instance
> > > >> already has sp1 though. Thanks and appreciate your very quick response.
> > > >>
> > > >> "Kaisa M. Lindahl Lervik" wrote:
> > > >>
> > > >> > OK, seems like someone else had the same problem a few weeks ago. His
> > > >> > problem and solution:
> > > >> >
> > > >> > I had the same problem.
> > > >> > It was caused by that I had installed reporting services after I had
> > > >> > run
> > > >> > SP1 on SQL Server 2005.
> > > >> >
> > > >> > Solved it by runing SQL Server 2005 SP1 again.
> > > >> >
> > > >> >
> > > >> > Hope this helps!
> > > >> >
> > > >> > (At the end of this thread:)
> > > >> > http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/f94ed9da97f6cf0a/
> > > >> >
> > > >> > Kaisa
> > > >> >
> > > >> > "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > > >> > news:3EDD6003-1110-4BC5-9887-793C480A97C9@.microsoft.com...
> > > >> > >I am installing rss 2005 on a SQL Server 2005 database, please help
> > > >> > >
> > > >> > > "Kaisa M. Lindahl Lervik" wrote:
> > > >> > >
> > > >> > >> By the error message, it seems you're trying to install the RS 2005
> > > >> > >> database to a database instance running SQL Server 2000. This seems
> > > >> > >> to be
> > > >> > >> possible, but you have to do things differently during setup. This
> > > >> > >> article might help you in the right direction:
> > > >> > >> Using SQL 2000 for SSRS 2005 metadata storage
> > > >> > >>
> > > >> > >>
> > > >> > >> When setting up SQL Server Reporting Services 2005, can you use SQL
> > > >> > >> 2000
> > > >> > >> as the host for the reportserver database? Yes, you can (with an
> > > >> > >> obvious
> > > >> > >> caveat in one scenario).
> > > >> > >>
> > > >> > >>
> > > >> > >>
> > > >> > >> https://blogs.msdn.com/bimusings/archive/2006/03/29/564173.aspx
> > > >> > >>
> > > >> > >>
> > > >> > >> Kaisa M. Lindahl Lervik
> > > >> > >>
> > > >> > >>
> > > >> > >> "Piku" <Piku@.discussions.microsoft.com> wrote in message
> > > >> > >> news:8B4C1C74-8DB4-4287-8A95-445EA14A1FF3@.microsoft.com...
> > > >> > >> > In Reporting Server2005 Configuration, while verifying database
> > > >> > >> > version
> > > >> > >> > and
> > > >> > >> > trying to upgrade it Getting Msg : "The DATABASE VERSION C.0.8.40
> > > >> > >> > does
> > > >> > >> > not
> > > >> > >> > match your reporting server installation. you must upgrade your
> > > >> > >> > reporting
> > > >> > >> > services database.
> > > >> > >> >
> > > >> > >> > Please help, can not move forward.
> > > >> > >> >
> > > >> > >> > Regards...Piku
> > > >> >
> > > >> >
> > > >> >
> > >
> > >
> > >