Summary:
Resolution: Fixing "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. errors is a really difficult task for most computer users. To solve "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. problems effectively and efficiently, install a good "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. Error Removal Tool is a smart solution. This is definitely your ideal tool to solve "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. problem in the shortest time.
Download the "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. repair tool
In order to repair "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. problem, install SmartPCFixer immediately. This system optimizer software is already proven to locate, identify, and fix "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. errors. Speed up your PC with SmartPCFixer at once
Manual Resolutions
SYMPTOMSThe Dexterity built 3rd party product was created using an installation script that creates palette items and tables for the product.
The installation script is automatically run when the chunk file is expanded and occurs before user authentication to Great Plains.
During the installation, the error message "Specified owner name 'DBO' either does not exist or you do not have permission to use it" is given.
This halts installation and no palette items are created.
Enabling the dexsql.log using Knowledge Base Article reveals that the code is trying to create the Palette Master table (SY00200) which already exists on the system however this same code works correctly on a Microsoft SQL installation installed as case insensitive.
An excerpt of the dexsql.log shows the error:
/*
Date: 11/24/2003
Time: 11:09:35
stmt(26822344):*/
CREATE TABLE TWO.DBO.SY00200 (PALSQNUM smallint NOT NULL, PALPMTNM char(21) NOT NULL, PALCMDTP smallint NOT NULL, PALETCMD char(255) NOT NULL, APLICFIL char(255) NOT NULL, DICTID smallint NOT NULL, Language_ID smallint NOT NULL, PaletteID smallint NOT NULL, PaletteDictID smallint NOT NULL, DEX_ROW_ID int identity NOT NULL)
/*
/*
Date: 11/24/2003
Time: 11:09:35
SQLSTATE:(37000) Native Err:(2760) stmt(26822344):*/
[Microsoft][ODBC SQL Server Driver][SQL Server]Specified owner name 'DBO' either does not exist or you do not have permission to use it.*/
The installation script is shown below.
local integer l_result;
local string l_translate;
call Initialize; Set the default System pathnames
get first table SY_Company_MSTR;
while err() <> EOF do
set 'Company ID' of table SY_Pathnames to 'Company ID' of table SY_Company_MSTR;
set 'File Series' of table SY_Pathnames to 8; Company
get file SY_Pathnames;
l_translate = 'Data Pathname' of table SY_Pathnames;
call Translate_Pathnames, l_translate;
'Series Pathnames'[8] of globals = l_translate;
l_result = productInUse() of form LibRegistration;
call RP_CreatePalette; creates Palette Items
call RP_Tables_Creation; creates custom tables
get next table SY_Company_MSTR;
end while;
CAUSE
The problem is seen only due
to the case sensitive installation of Microsoft SQL and the uppercase "DBO" being sent.
In a case insensitive system, TWO.DBO.SY00200 and the more typical TWO.dbo.SY00200 are the same which is why the same code works correctly on that system.
However on a case sensitive system, the TWO.DBO.SY00200 table was not found due to the case sensitivity and the table was being created automatically by Dexterity when accessed.
However the owner name 'DBO' didn't exist (but the owner name dbo does) causing the error.
Debugging the code, the correct path of TWO/dbo/ is being returned in the 'Data Pathname' of the table SY_Pathnames.
The problem
occurs when
calling the Translate_Pathnames procedure which is normally only called for ISAM databases that use mapped drives for data paths.
The Translate_Pathnames script does properly abort without modifying the l_translate path parameter under the SQL database but at the time this occurs the system has not initialized the 'SQL Server' of globals to be greater than 0 and therefore appears to the procedure as running under an ISAM database.
Because the system appears to be ISAM, the l_translate path variable is being changed from TWO/dbo/ to TWO/DBO/ and when the tables is accessed it is then using TWO.DBO.SY00200 instead of the proper table name.
RESOLUTION
The function productInUse() of form LibRegistration determines the correct database and sets the 'SQL Server' of globals properly.
The function was being called but only after the incorrect paths had been set.
Changing the code slightly to call the function earlier solved the problem.
local integer l_result;
local string l_translate; call Initialize; Set the default System pathnames
l_result = productInUse() of form LibRegistration; assign database type before table access
get first table SY_Company_MSTR;
while err() <> EOF do
set 'Company ID' of table SY_Pathnames to 'Company ID' of table SY_Company_MSTR;
set 'File Series' of table SY_Pathnames to 8; Company
get file SY_Pathnames;
l_translate = 'Data Pathname' of table SY_Pathnames;
call Translate_Pathnames, l_translate;
'Series Pathnames'[8] of globals = l_translate;
call RP_CreatePalette; developer added code to create Palette Items
call RP_Tables_Creation; developer added code to create custom tables
get next table SY_Company_MSTR;
end while;
This article was TechKnowledge Document ID:
34042
What Else Does SmartPCFixer Offer You?
Apart from fixing "Specified owner name 'DBO' either does not exist or you do not have permission to use it" error message creating palette items in a Dexterity installation script. problems, SmartPCFixer is designed to provide the user's computer system with better optimization, which helps you manage startup items, desktop, browser objects, Internet, system service, Windows optimization, file extensions and so on. With these sophisticated utilities your system is tuned up to run at the optimal state.
SmartPCFixer is designed to scan, diagnose and repair your operating system. Using it results in better optimization, manages startup and desktop, assists you with maintaining browser objects, internet options, system service, and repairs file extensions. With this arsenal of powerful, sophisticated utilities your system is tuned to run at its optimal state. Included are Easy Repair Wizard, Error Utilities, File Association fixer, Register ActiveX, Shortcuts Fixer, Winsock2 Repair toolkit, Dll Fixer and more.
Related: Microsoft Upgrade,Do System Restore,0x80072efd,Printer Spooler,Upgrade Window
Read More: ,it windows update,Advrcntr2.dll,directx download,disable pop up blocker internet explorer,window 10 download
コメント