August 18, 2003 at 9:22 am
I followed Andy Warren's article on moving a sqlserver to a new box. both os are the same the drives are the same and sqlserver service packs are the same. By copying the databases to a new server and then installing sql server 2000 to the new machine and then renaming the program directory to old and copying the program directory from the old machine over. Everything looked fine but some of the jobs and some dts packages will not work. I get the error The instruction at 0x77fcc97c referenced memory at 0xfffffff9 the memory could not be read. any help is greatly appreciated.
thanks
August 18, 2003 at 10:07 am
Do they run manually (interactively) or as scheduled jobs or both?
What is in the packages that doesn't work?
Steve Jones
August 18, 2003 at 10:21 am
Only certain jobs will not run manually or by schedule. Some jobs will run fine.The packages will run. Although sometimes the done box does not come up, when i am in design mode and running a package, it then just then pops me right out of em. The tasks in the packages are data pulls from informix and accubol systems we have. Some of the jobs are successfull going against informix and accubol and some are not. there seems to by now rythme or reason.
August 19, 2003 at 6:39 am
quote:
I followed Andy Warren's article on moving a sqlserver to a new box. both os are the same the drives are the same and sqlserver service packs are the same. By copying the databases to a new server and then installing sql server 2000 to the new machine and then renaming the program directory to old and copying the program directory from the old machine over. Everything looked fine but some of the jobs and some dts packages will not work. I get the error The instruction at 0x77fcc97c referenced memory at 0xfffffff9 the memory could not be read. any help is greatly appreciated.thanks
August 19, 2003 at 6:44 am
I am new to SQL but I was just tasked with moving a database from one server to another. I used sp_detach_db and sp_attach_db then copied the database to the new server. I then ran a script I found that migrates all users ID's and passwords. here is thatr script. Don't know if this helps.
sp_dropuser TAG1
go
sp_dropuser administrator
go
sp_droplogin TAG1
go
sp_droplogin administrator
go
sp_droplogin Q
go
sp_addgroup Quantum
go
sp_addlogin 'administrator', 'password'
go
sp_adduser administrator,administrator,Quantum
go
sp_addlogin 'TAG1', 'WLV818'
go
sp_adduser TAG1,TAG1,Quantum
go
sp_addlogin 'Q', 'QAdmin'
go
sp_grantdbaccess 'Q', 'Q'
go
sp_addrolemember 'db_owner', 'Q'
go
/**************************************************
All Application users
***************************************************/
sp_dropuser example
go
sp_addlogin 'example', 'password'
go
sp_adduser example,example,Quantum
go
quote:
I followed Andy Warren's article on moving a sqlserver to a new box. both os are the same the drives are the same and sqlserver service packs are the same. By copying the databases to a new server and then installing sql server 2000 to the new machine and then renaming the program directory to old and copying the program directory from the old machine over. Everything looked fine but some of the jobs and some dts packages will not work. I get the error The instruction at 0x77fcc97c referenced memory at 0xfffffff9 the memory could not be read. any help is greatly appreciated.thanks
August 19, 2003 at 8:02 am
it seems the offending jobs have certain packages that stop the job. when i go into dts design view, the packages seem to run and all the tasks will complete but the gears graphic just keeps on turning and eventually i am exited from em altogether. I have tried to create new jobs and use the packages with no luck. The server will get the message dtsrun.exe application error. The memory cannot be read. I have also redone some of the packages from scratch by copying the objects from the offending package and pasting into a new package and again i get the same error. For the most part most of the jobs run fine. Could it be some sort of jobid or packageid guid. Is there a way to find this out. Thanks
August 19, 2003 at 5:14 pm
If you moved the actual MDF, all should be fine. Is the server name the same?
Andy
August 20, 2003 at 5:20 am
Yes the server name is the same. I scripted out the jobs and recreated them, still with no luck. The new server is using hyperthreading but i dont think that should be a problem with sql2000sp3.
August 21, 2003 at 12:38 pm
Well i tried to rebuild the sqlserver registry entries i got this error
sqldumper.exe entry point not found
The procedure entry point mindumpwritedump could not be located in the dynamic link library dbghelp.dll. any ideas
August 22, 2003 at 10:43 am
well i finally got the problem jobs to run. Microsoft Knowledge Base Article 318819 seems to have done the trick . well see if this got it. But you have to set the packages to execute in the main thread. Im not sure if this has to do with the hyperthreading or not. thanks
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply