6.5.3 and SQL 2008

Has anyone tried to use 6.5.3 with SQL 2008. I know infor says it dosent support it, but wondering if anyone has done it. I am building a new server and just installed SQL 2008 and managed to dump the 6.5.3 database into SQL 2008. I have installed visual 6.5.3 and it seems to give me an error 19005. I think it has something to do with rights. Because when i replace the sql.ini file with the old server name (since its on the network visual works, but when I point the sql.ini file to the new server it dosent.

Find more posts tagged with

VISUAL - Enterprise General Discussions

Comments

unknown

Did you establish a visual user account on the new sql 2008 server that has dbo ownership rights to the new database?

Are you coming from MS sql 2005 to MS sql 2008. if so did you export/copy the database?
If you tried it this way it would have errored if you had not established an associated user account with the old database on the new server prior to doing the copy.

Did yopu export the database as "SA" and import it as "SA" ?

I've gone MS to MS sql migrations just with the copy/export okay. However I had to establish the database users on the new server ahead of time.

The when we exercised the copy/export to the new database it would prompt for the user account to use for the migration.

anyhow, just some thoughts don't know if it will help

cheers
Keith

Just checking.

kelly-degobbi

This is what I did if I can remember LOL
We were currently using SQL 2000 with visual 6.5.3
I did a backup of the data base and called it date.bak
I then moved it to the new server.
I created a VMFG data base in SQL 2008
It has the sa and SYSADM account
I did a restore into the VMFG with the backup copy
I then went into the SQL.ini and changed ot to point to the new server
Tried to login as sysadm and get the error 19005 password may be wrong, data base ect,,
I then pointed the SQL.ini file to the old server and it worked
So it has something to do with rights

There was no export or import just a backup
I am also trying now to creat new user accounts but it seems not to work...

unknown

There used to be a document on the Infor site for deleting all users and adding them back in to maintain user rights. I actually had to delete all users except DBO then add them back into Visual with the same user name. After all users were added back in run Fix Synonyms and Grants they should be good to go. I did have a few users I actually had to change the users password for them before they could login to Visual. Make sure you are testing.

seanr

Hi,

This is what I do when creating new instances of SQL server.

It will work to transfer all username and password between servers of any SQL Server version.

Before restoring your database on the new server

No logins, including SYSADM, need to be pre-created.

On your current production server.
1) Create the sp_help_revlogin proceedure in Method 1

support.microsoft.com/.../246133

Method 1 will work for Visual because the ERP system handles all security.

2) Run the proceedure on your current production system.
3) Copy the output to query anaylyzer on your new server.
4) Run the script on the new server - All usernames and password will now be restored to your new server.
5) Restore your database to the new server.
6) Open the restored database tree in Microsoft Management Studio
7) Select the tables folder
8) In Object explorer detail, Sort view by schema
9) Go down to the bottom and select all tables owned by the SYSADM Schema
10) Right click and select delete(DROP) and drop the tables. They are all temp tables the Visual did not clean up after use.
11) Go to Security, in the restored database, highlite users folder.
12) Select the SYSADM user and right click to Delete(DROP) including Schema objects, in object explorer detail
13) Go to Security, Instance security, and highlite logins
14) Right click the SYSADM user and select properties.
15) Go to "User Mappings"
16) In the top half, select the new visual database.
17) In the bottom half, Select db_owner and, for SQL Server 2005 above, db_securityadmin.
18) Select OK
19) Log into your new instance of Visual, on the new server, as SYSADM or any current Visual user.
( Make sure your SQL.ini file is pointing to the new server)

Sean

unknown

good post Sean... you beat me to it.. I was over at MS looking at account migration and came back and you had posted up!!

cheers
Keith

Koch Industries Talent Acquisition Transformation -20200827 1801-1.mp4

kelly-degobbi

OK I have tried and tried to get this work, but no success. I decided to just uninstall visual and the SQL 2008 from the server and start all over again.
This is where I am at
I set up SQL 2008
Created the new data base VMFG with sysadm rights
Installed visual 6.5.3
Changed the sql.ini file to point to the new server
The ini file looks like this:

[dbnt1sv]
servername=Server1,sqlapipe
dbname=ISLAND,sqlapipe

[dbnt1sv.dll]
comdll=sqlapipe

[dbnt1sv.apipe]
;debug=15,dbntsrv.dbg

[win32client]
clientname=Win32Client

[win32client.dll]
comdll=sqlapipe

[win32client.apipe]
;debug=15,client.dbg

[sqlserver]
VMFG=AFIRALSRV03VISUAL,VMFG

It still wont let me log in
Its an empty data base as well

Buuuttt when I point it to the old server AFIRALSRV01 is works...go figure

Any ideas guys...

seanr

Hi,

You old server AFIRALSRV01 is running SQLbase?

Your sql.ini file looks like a sqlbase connection file.

This connection info is telling Visual to connect to the server using sqlpipe, which might not be turned on in SQL server by default.

Here is my sql.ini file that points to a sql server named database on the network.

[SQLSERVER]
VMFG=servername,VMFG

;ODBC Gateway Section
[odbcrtr]
; this is needed by Visual Quality
remotedbname=VQMS,DSN=VQMS

[winclient]
clientname=client
connecttimeout=5

[winclient.dll]
comdll=sqlwsock

[winclient.wsock]
serverpath=severname,ipaddress of server/*

[win32client]
clientname=Win32User
setzerolengthstringstonull=on

[win32client.dll]
comdll=sqlodb32
comdll=sqlws32

[win32client.ws32]
serverpath=severname,ipaddress of server/*

;if the database and the exe's are on the
;same computer, you could try
;localhost as the servername and 127.0.0.1
;as the ip address.

unknown

I pulled my hair out over a similar problem. I had sql2000 and installed sql2008 on the same box and couldn't get it to work just like you. My problem was that I was using the wrong server name:

[sqlserver]
VMFG=VISUAL,,OLDDB
VMFG=VISUALMSSQLSVR,NEWDB
VMFG=VISUALMSSQLSVR2,,NEWDB

I suspect you are having the same issue. Here is how I found the 'correct' server name (VISUALMSSQLSVR2) for my instance of sqlserver2008: I went to the ODBC (data sources) and went to add a new system DSN . Choose the sql server driver and then goto the: "Which SQL Server do you want to connect to" and use the pulldown to see the servers. If you had the same problem as me I bet you will see something other than "AFIRALSRV03VISUAL"

Oh... and as always, make sure that you only have one sql.ini file on your server.

Hope this helps.

Scott

kelly-degobbi

Ok i tried your ini file sean and it still dosent work, can you look at my paste below and elt me know if I set it up right. As for Scott, i looked under the OBDC and it lists my server AFIRALSRV03 and my other two servers but nothing like your yours.

VMFG=AFIRALSRV03,VMFG

;ODBC Gateway Section
[odbcrtr]
; this is needed by Visual Quality
remotedbname=VQMS,DSN=VQMS

[winclient]
clientname=client
connecttimeout=5

[winclient.dll]
comdll=sqlwsock

[winclient.wsock]
serverpath=localhost,127.0.0.1/*

[win32client]
clientname=Win32User
setzerolengthstringstonull=on

[win32client.dll]
comdll=sqlodb32
comdll=sqlws32

[win32client.ws32]
serverpath=localhost,127.0.0.1/*

;if the database and the exe's are on the
;same computer, you could try
;localhost as the servername and 127.0.0.1
;as the ip address.

seanr

Hi,

Above this
VMFG=AFIRALSRV03,VMFG
You need to have [SQLSERVER]

The line should be
[SQLSERVER]
what you want to call your Visual DB=servername, what your visual DB is called in sql server

I have a server with the exe and the database both on them and the sql.ini file is set-up exactly like you have it with the exception of the [SQLSERVER]
Instead of using the servername AFIRALSRV03, use localhost

[SQLSERVER]
V700=LOCALHOST,V700
V654=LOCALHOST,V654

; ODBC Gateway Section
[odbcrtr]
remotedbname=VQMS,DSN=VQMS

[winclient]
clientname=client
connecttimeout=5

[winclient.dll]
comdll=sqlwsock

[winclient.nbiow]

[winclient.spxw4]

[winclient.wsock]
serverpath=FABRIS38,127.0.0.1/*

[win32client.comments]
;
; Win32 (Windows 95 or NT)
;--------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlntnbi REMOTE database using NetBios
; sqlws32 REMOTE database using TCP/IP (WinSock)
; sqlspx32 REMOTE database using IPX/SPX (Win32 Novell Client)
; sqlwsspx REMOTE database using IPX/SPX (Win32 Microsoft Client)
;
[win32client]
clientname=Win32User
setzerolengthstringstonull=on

[win32client.dll]
comdll=sqlodb32
comdll=sqlws32
;comdll=sqlapipe
;comdll=sqlwsspx
;comdll=sqlntnbi
;comdll=sqlspx32

[win32client.ws32]
serverpath=FABRIS38,127.0.0.1/*

[win32client.apipe]

[win32client.ntnbi]

[win32client.ws32]

[win32client.spx32]

[win32client.wsspx]

***********
Sean

kelly-degobbi

I finaly fixed my sql.ini file. I now have 6.5.3 loaded and its working with my data base. But now my problem is that it only works with SYSADM. I did some research on orphaned ID's and have followed all the steps. But one thing I have noticed is that when I run the orphaned ID report it comes up with none. I know they are orphaned casue the no users have rights. BUt it seems even when I try to create a new user ID in the logins section is still comes up with that error ID already exists. I even tried to delete the user and make a new one and the errors still keep coming...any ideas??

Copyright © 2025 Infor. All rights reserved.