Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 10 of 17 total |
Error 11293 |
Mon, Aug 17 2009 11:43 AM | Permanent Link |
"Robert" | I am trying to set up a new database (DBserver 4.25 build 4) the dbserver
and the utility are running on computer A, the database is on computer B. I get an error 11293, I have tried both using UNC and mapping a drive. Any ideas? Robert |
Wed, Aug 19 2009 3:51 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< I am trying to set up a new database (DBserver 4.25 build 4) the dbserver and the utility are running on computer A, the database is on computer B. I get an error 11293, I have tried both using UNC and mapping a drive. >> The issue could be caused by a failure of the database server to create the specified database directory, which may not be the case if you are trying to point to an existing database/directory. If that is the case (already exists), then the only other reason for such an error would be that the database name is invalid or already exists. What is the database name that you're using ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Aug 19 2009 4:54 PM | Permanent Link |
"Robert" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:48DACCFE-E045-4202-B268-616F574B59DB@news.elevatesoft.com... > Robert, > > << I am trying to set up a new database (DBserver 4.25 build 4) the > dbserver and the utility are running on computer A, the database is on > computer B. > > I get an error 11293, I have tried both using UNC and mapping a drive. >> > > The issue could be caused by a failure of the database server to create > the specified database directory, which may not be the case if you are > trying to point to an existing database/directory. If that is the case > (already exists), then the only other reason for such an error would be > that the database name is invalid or already exists. What is the database > name that you're using ? > The error says "invalid or blank". The database folder is selected from the droptdown. If I move the database to the server, then I can create the database OK. But if I edit the database and try to point it back to the database in computer B (either by keying in a UNC name or by using a mapped drive and selecting from the directory dropdown) then I get the error again. So obviously an invalid file name is not "the only reason". What other possiblities are there? File name too long? Embeded blanks? Robert > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Wed, Aug 19 2009 5:13 PM | Permanent Link |
"Robert" | "Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message news:AB94942E-D725-43DA-9C7E-A9184CA94C15@news.elevatesoft.com... > > > What other possiblities are there? File name too long? Embeded blanks? That's it. If I create another mapped drive directly to the database on the other computer (bypassing all the rest of the folder names and backslaches) then it works OK. Iif it is not on this computer, then it has to be something like W:\ Robert |
Fri, Aug 21 2009 11:53 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< The error says "invalid or blank". The database folder is selected from the droptdown. If I move the database to the server, then I can create the database OK. But if I edit the database and try to point it back to the database in computer B (either by keying in a UNC name or by using a mapped drive and selecting from the directory dropdown) then I get the error again. So obviously an invalid file name is not "the only reason". >> Is there any particular reason that you come here and ask for assistance, only to criticize the assistance that I give you ? I didn't say "invalid file name", I said "invalid database name". Databases are simply logical constructs in the DBISAM Database Server, there aren't any files involved at all. This is the code: Result:=False; DirectoryError:=False; if (not FDatabases.Find(DatabaseName,DatabasePos)) then begin if (DataPath <> '') and (not DirectoryExists(ExpandFileName(DataPath))) then Result:=ForceDirectories(ExpandFileName(DataPath)) else Result:=True; DirectoryError:=(not Result); if Result then begin TempDatabase:=TConfigDatabase.Create(Self); with TempDatabase do begin Description:=DatabaseDescription; Path:=ConvertSlashes(DataPath); end; FDatabases.AddObject(DatabaseName,TempDatabase); FIsDirty:=True; WriteToFile; end; end; If Result=False, then the 11293 error is returned in the calling procedure. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Aug 21 2009 11:56 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< That's it. If I create another mapped drive directly to the database on the other computer (bypassing all the rest of the folder names and backslaches) then it works OK. Iif it is not on this computer, then it has to be something like W:\ >> That isn't a requirement of DBISAM, so there must be something environmental that is causing an issue with the path in terms of DirectoryExists() failing to work properly. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Aug 21 2009 1:00 PM | Permanent Link |
"Robert" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:3C6C5F8A-C62B-420D-AB18-C25FD2E9EA2B@news.elevatesoft.com... > Robert, > > << The error says "invalid or blank". The database folder is selected from > the droptdown. If I move the database to the server, then I can create the > database OK. But if I edit the database and try to point it back to the > database in computer B (either by keying in a UNC name or by using a > mapped drive and selecting from the directory dropdown) then I get the > error again. So obviously an invalid file name is not "the only reason". > >> > > Is there any particular reason that you come here and ask for assistance, Yeah, the particular reason is that this is a DBISAM Client Server group and I'm having trouble with a DBISAM Client Server program. Called Bill Gates at home, but he said he could not help me on this one, so here I am. > only to criticize the assistance that I give you ? I didn't say "invalid > file name", I said "invalid database name". Databases are simply logical > constructs in the DBISAM Database Server, there aren't any files involved > at all. > I wrote a small test program, running on the same computers, same identical environment, and both forcedirectories and directoryexists return true. With the same identical directory that fails in the server utility. This is the code procedure TForm1.Button1Click(Sender: TObject); begin if not sd.Execute then exit; <<<sd is a directory select dialog edit1.Text := ExpandFileName(sd.Directory); if DirectoryExists(edit1.Text) then showmessage('found') else showmessage('NOT FOUND'); if ForceDirectories(edit1.Text) then showmessage('forced') else showmessage('NOT forced'); end; Robert |
Mon, Aug 24 2009 1:06 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< Yeah, the particular reason is that this is a DBISAM Client Server group and I'm having trouble with a DBISAM Client Server program. Called Bill Gates at home, but he said he could not help me on this one, so here I am. >> You have taken what I said completely out of context. Don't misrepresent my statements. What I asked was why you ask for assistance *and then* criticize the assistance that you get. See the difference in context ? << I wrote a small test program, running on the same computers, same identical environment, and both forcedirectories and directoryexists return true. With the same identical directory that fails in the server utility. >> What version of Delphi are you using ? The DBISAM Database Server code is compiled in Delphi 5, by default. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Aug 24 2009 1:19 PM | Permanent Link |
"Robert" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:E68362DE-AA43-4752-98B6-11322B8C10D2@news.elevatesoft.com... > Robert, > > << Yeah, the particular reason is that this is a DBISAM Client Server > group and I'm having trouble with a DBISAM Client Server program. Called > Bill Gates at home, but he said he could not help me on this one, so here > I am. > >> > > You have taken what I said completely out of context. Don't misrepresent > my statements. What I asked was why you ask for assistance *and then* > criticize the assistance that you get. See the difference in context ? Look Tim, I did not "criticize" anything, simply stated that given what I observed (the fact that if I mapped the database as a drive it works, but if it a drive plus directories, or UNC, then it does not) your theory appeared to be incorrect. > > << I wrote a small test program, running on the same computers, same > identical environment, and both forcedirectories and directoryexists > return true. With the same identical directory that fails in the server > utility. >> > > What version of Delphi are you using ? The DBISAM Database Server code is > compiled in Delphi 5, by default. > D6. Robert |
Mon, Aug 24 2009 2:15 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< Look Tim, I did not "criticize" anything, simply stated that given what I observed (the fact that if I mapped the database as a drive it works, but if it a drive plus directories, or UNC, then it does not) your theory appeared to be incorrect. >> It's not a "theory", and I'm not trying to be "correct" about anything. I'm trying to go through the possible scenarios to explain what you're seeing, and you seem very displeased with the fact that I'm not telling you what you want to hear. What do you want me to say ? That it's a bug when there's no evidence that this is the case ? << D6. >> The source code for both D5 and D6 are identical for both DirectoryExists and ForceDirectories. -- Tim Young Elevate Software www.elevatesoft.com |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |