The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Cannot create remote db from host using MSDE instance
Posted: 10 Apr 07 10:11 AM
|
I think there may be a permissions problem somewhere but I've called slx ts and we went through a number of things, I was on the phone with them for 3 hours and we're still reasearching. I knew I should of came here earlier but my loss....
Trying to create a remote db from an MSDE instance. I've double and triple checked all the sysdba and sa password and also made sure there are no leading blanks on the username, etc. The host and msde have the same service pack.
[04/10/2007 10:06:14 AM]Detaching remote db...
[04/10/2007 10:06:14 AM]Detaching remote DB error: The database 'SLX_charbaugh' does not exist. Use sp_helpdb to show available databases
Database creation cancelled.
Also on the msde instance machine I get the following application event failures. Also I get audit sucesses on the host when the admin on the msde instance machine connects. There seem to be no failures at the host, only the desktop admin machine.
17204 :
FCB::Open failed: Could not open device c:\SLX_charbaugh_dat.mdf for virtual device number (VDN) 0.
17207 :
udopen: Operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device c:\SLX_charbaugh_dat.mdf.
pls any ideas would help
|
|
|
| |
|
Re: Cannot create remote db from host using MSDE instance
Posted: 11 Apr 07 5:32 PM
|
fiogf49gjkf0d I've seen all of those error messages on multiple remote creations and never considered it a problem. The mdf/ldf files are created and they attach to remotes so the error messages didn't make much sense.
We currently have only one server. It's the SLX, SQL Server, and hosts Administrator and a copy of the client as well. You mentioned "desktop admin machine" which suggests that unlike us, you at least have a separate machine for Administrator. Because of this you likely use MSDE to create the instance, whereas we use straight SQL Server.
Have you tried looking over C:\Program Files\SalesLogix\RemoteDB_DTS.sql? It's the file that MSDE/SQL uses to create the remote database. If there are any serious errors, it should more than likely boil down to the file.
Anyway I'm saying this not to suggest you don't have a legitimate concern, but the databases I've made with the same error messages have ran perfectly fine. Perhaps it is a permissions issue or some configuration setting but for some reason I couldn't find it. At the time though, patience was never a factor in the equation. I had to have the remotes created so regardless of what errors I was getting, if they worked I had to deploy them. |
|
|
|
Re: Cannot create remote db from host using MSDE instance
Posted: 12 Apr 07 9:48 AM
|
fiogf49gjkf0d Wow, thanks for that post - I just realized, by looking in the file, that in the third SQL statement down, my sysdba password was being stored in plain text. I'm glad I found that. Also, it is very nice to know what script is being run just in case I do have any problems... |
|
|
|
Re: Cannot create remote db from host using MSDE instance
Posted: 13 Apr 07 10:36 AM
|
fiogf49gjkf0d When you create the DTS package later (whatever setting it is called), it'll just create this file that you can then manually run later. The only issue I've had with it is that the file isn't removed automatically. It's most likely done that way so you have the option of viewing the file later but it does create a liability, especially if people have read access to the Program Files\SalesLogix folder on that particular computer. |
|
|
|
Re: Cannot create remote db from host using MSDE instance
Posted: 14 Apr 07 9:14 AM
|
fiogf49gjkf0d As the doctor says.. when does it hurt.. you say whe I do "this".. so don't do it (don't use create later).
Oh yes, there is a major hole in using create later that can introduce data problems. If a script is set to fire later and synch is still "active" and runs.. you have a high probablility of having a bad cut.
We use the "later" feature ONLY for debugging purposes and we teach ALL of our clinets to never use it for normal work.
--
rjl |
|
|
|