It is currently 21. Nov 2018, 08:57


[Solved:] Upgrade -> 6.4 Stored procedure SP_RENAME Error

Version v6.6.5 has been released in May 2016 - EOL since end of 2016!

Moderator: Moderator Team

  • Author
  • Message
Offline

philcraigde

Activist

Activist

  • Posts: 11
  • Joined: 13. Apr 2010, 11:57

[Solved:] Upgrade -> 6.4 Stored procedure SP_RENAME Error

Post20. Jan 2015, 15:39

I attempted to upgrade my 6.3.1 Version to and consistently recieve the following error Message "Could not find stored procedure SP_RENAME."

I am using an external MS SQL database and have tried both the full and compact packets with the same result. i am running the upgrade with the admin user who has full rights to the Database.

the installation runs to Completion and when i start the Configuration I see a message that i have an database incompatability.
Offline

philcraigde

Activist

Activist

  • Posts: 11
  • Joined: 13. Apr 2010, 11:57

Re: Upgrade -> 6.4 Stored procedure SP_RENAME Error

Post20. Jan 2015, 15:48

from Windows Application Log

Service cannot be started. Login.Ventory.Data.ObsoleteDatabaseException: The database 'LogInventory_6' has version 6.3.0, which is lower than the minimal version supported by this product (6.4.0).
at Login.Ventory.Data.Model.InventoryData.ValidateDatabase()
at Login.Ventory.Data.DataContext.CheckDatabase()
at Login.Ventory.DataService.DataService.<.ctor>b__4()
at Login.Ventory.DataService.DataService.Execute(Boolean dispose, Boolean throw, Action action)
at Login.Ventory.DataService.DataService..ctor(Boolean throwOnCriticalError)
at Login.Ventory.DataService.DataService.StartNew(Boolean throwOnCriticalError)
at Login.Ventory.DataService.Service.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
Offline
User avatar

StefanS

Moderator

Moderator

  • Posts: 228
  • Joined: 1. Jul 2009, 10:58

Re: Upgrade -> 6.4 Stored procedure SP_RENAME Error

Post21. Jan 2015, 11:05

Hello,

we think it's a problem with your permissions. Perhaps you have full rights to your database but not to the stored procedure "sp_rename" in the master database. Below you can see what the upgrade script does. You can rename the table by using the UI of SQL Management Studio or a tool like that instead of using the sp_rename procedure. After finishing this upgrade process you have to update the database version to '6.4.0' in the table '_TE9HSU52ZW50b3J5'. After all the LOGINventory modules will work as expected. It's strongly recommended to backup your database before upgrading! We hope this will help you. If you have any questions please do not hesitate to contact us anytime.

Code: Select all
ALTER TABLE [_LicenseInfo] DROP [LicenseInfo_Node];
EXEC SP_RENAME '_LicenseInfo', '__LicenseInfo';
create table [dbo].[_LicenseInfo] (
    [Id] [uniqueidentifier] not null,
    [NodeId] [uniqueidentifier] not null,
    [Name] [nvarchar](128) not null,
    [Amount] [int] not null,
    [LicenseClass] [nvarchar](128) not null,
    [UpgradeRight] [int] not null,
    [DowngradeRight] [int] not null,
    [ValidFrom] [datetime] null,
    [ValidTo] [datetime] null,
    [Submission] [datetime] null,
    [SoftwareId] [nvarchar](max) null,
    [TechContact] [nvarchar](max) null,
    [ProfContact] [nvarchar](max) null,
    [AquisitionCosts] [int] null,
    [MaintenanceCosts] [int] null,
    [OrderDate] [datetime] null,
    [OrderNumber] [nvarchar](50) null,
    [InvoiceNumber] [nvarchar](50) null,
    [InventoryNumber] [nvarchar](50) null,
    [Supplier] [nvarchar](128) null,
    [Comment1] [nvarchar](max) null,
    [Comment2] [nvarchar](max) null,
    [Comment3] [nvarchar](max) null,
    [Url] [nvarchar](2000) null,
    [Configuration] [nvarchar](max) null,
    primary key ([NodeId], [Id])
);

alter table [dbo].[_LicenseInfo] add constraint [LicenseInfo_Node] foreign key ([NodeId]) references [dbo].[_NodeInfo]([Id]) on delete cascade;

INSERT INTO [_LicenseInfo] ([Id], [NodeId], [Name], [Amount], [LicenseClass], [UpgradeRight], [DowngradeRight], [ValidFrom], [ValidTo], [Submission], [SoftwareId]
, [TechContact], [ProfContact], [AquisitionCosts], [MaintenanceCosts], [OrderDate], [OrderNumber], [InvoiceNumber], [InventoryNumber],
[Supplier], [Comment1], [Comment2], [Comment3], [Url], [Configuration])
SELECT [Id], [NodeId], [Name], [Amount], [LicenseClass], [UpgradeRight], [DowngradeRight], [ValidFrom], [ValidTo], [Submission], [SoftwareId]
, [TechContact], [ProfContact], [AquisitionCosts], [MaintenanceCosts], [OrderDate], [OrderNumber], [InvoiceNumber], [InventoryNumber],
[Supplier], [Comment1], [Comment2], [Comment3], [Url], [Configuration] FROM [__LicenseInfo];

DROP TABLE [__LicenseInfo];
mfg
StefanS
Offline

philcraigde

Activist

Activist

  • Posts: 11
  • Joined: 13. Apr 2010, 11:57

Re: Upgrade -> 6.4 Stored procedure SP_RENAME Error

Post29. Jan 2015, 11:39

Good Morning,

It was definatley a permission Problem. I had previously tried the Installation using my Standard Admin user. I logged on locally using the Service user defined in the LogIn Configuration and the Installation ran successfully.

Thanks for your help. :D

Return to LOGINventory6 English

Who is online

Users browsing this forum: No registered users and 1 guest

cron