Can't run rskeymgmt after SP2

After installing SP2 for SQL 2005 I can no longer run rskeymgmt. I was
trying to backup the encryption key
(rskeymgmt -e -fc:\rsdbkey.txt -ppassword) but I get the following error:
The Report Server Windows service in not responding to RPC requests. The
service may not be running.
I have checked and the service is running. Are there any issues with SP2?On Apr 5, 1:21 pm, "Tim Kelley" <tkel...@.company.com> wrote:
> After installing SP2 for SQL 2005 I can no longer run rskeymgmt. I was
> trying to backup the encryption key
> (rskeymgmt -e -fc:\rsdbkey.txt -ppassword) but I get the following error:
> The Report Server Windows service in not responding to RPC requests. The
> service may not be running.
> I have checked and the service is running. Are there any issues with SP2?
This article might be helpful:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1323751&SiteID=1
Regards,
Enrique Martinez
Sr. Software Consultant

Can't make relation when Defining a Data Source View

I want to set the relation between two table when I defining a data source
view.
The type primary key is int and the forgien key is int32, then the relation
can't set.
They are all int type but just with different length.
How can I do?On Nov 24, 11:01 pm, "ad" <fly...@.wfes.tcc.edu.tw> wrote:
> I want to set the relation between two table when I defining a data source
> view.
> The type primary key is int and the forgien key is int32, then the relation
> can't set.
> They are all int type but just with different length.
> How can I do?
I'm not sure if I am following you correctly; however, in terms of
referential integrity (i.e., primary key to foreign key relationships)
the data types have to match quite closely. You could try casting one
of the fields to the other to make them match, of course, this may not
resolve your issue. Otherwise, you might want to change the datatype
of one of the fields to the other and use a constraint, etc to enforce
the original integer length. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Cant Keep Primary Key Columns when moving db to SQL 2005 from 2000

there are some primary key columns which are autoincrement in some tables.
for exampl page_id, now we have deleted many pages in old server so there
are many gaps between the page_id
even the it doest start with 1 because during the testing many initial pages
were deleted.

but when we move it to the new server with sql2005 it gives them numbers from 1,2,3 and
so on.

I need to keep existing 2000 keys. How can I acomplish this?

it would have worked if it also updates this number in other tables which
refer to this column
for example page_id is autoincreement in tbl_category_pages ( this table
contains the page information)
and it also appears in tbl_page_content ( this table contains the page's
content)

because it changes this number at one place and not the other place it makes
the database incorrect.

i tried many things ( there is even an option to keep the values of such
columns but doesnt seem to work)

Thanks,

WessTo maintain existing relationships, simply select all tables and copy them to a notepad. From there you just copy and paste them in the query anlyzer.|||If you want tables with relationships and data, take a complete back up of the database. Use that backup file and restore in sql 2005.|||ramasp,

Thanks, I appreciate your help.

I have given this information to the developer I have working on this. He tells me he tried this and that it can not work because the two versions are different.

Please let me know if this should work and the proccess to do so.

Thanks,

Wess

Cant Increment the Counter Registry Key for Setup in SQL Server 2005 (missing registry)

Hi im trying to install Sql Server 2005 but it says i need to Increment the Counter Registry Key for Setup in SQL Server 2005 before doing so.

Im following the guide at http://msdn2.microsoft.com/en-us/library/ms143215.aspx but in my registry the folder

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

doesnt contain any keys

"Last Counter"=dword:00000ed4 (5276)
"LastHelp"=dword:00000ed5 (5277)

or any key for that matter.

How can i fix this?

Two things if this is your development box make sure your files are saved and run system restore it is a clean way to remove problems in your system, if this is a company server tell the system team in charge of that server you need the registry fixed because at a bank I worked they had an enterprise wide registry cleaning software. Hope this helps.