forum pyry

[Gość: bocian]

czy forum kolejorz pyry klękło na amen ?? :)
a jeśli tak to wie ktoś dlaczego ??

[Gość: Marceli]

Prawdopodobnie jestes w sieci ICPNET - i to jest powód dlaczego nie ma forum.
Padła siec i z tego co wiem nie wiadomo kiedy zostanie ona zrobiona :(

[Gość: Muldgaard]

Ja też jestem z icpnetu :(( bo się załamię ...

[Gość: Goldi]

potwierdzam ICPNET zrobil nam kolejny mily prezent, oby tak dalej a firma
zamiast sie rozwijac bedzie sie uwsteczniac z powodu coraz mniejszej ilosci
klientow

czyzby znowu?:(

[Gość: klaifert]

[Gość: Marceli]

tak. Tym razem padła stona a nie siec. Robimy wszystko zeby jak najwczesniej
sytuacja wrocila do normy, Za zaistniale problemy - przepraszamy

[Gość: bocian]

rozumiemy i spokojnie czekamy na dostęp do forum
tylko że średnia postów na dzień mi spada :)

[Gość: DJanos]

Gość portalu: bocian napisał:

> czy forum kolejorz pyry klękło na amen ?? :)
> a jeśli tak to wie ktoś dlaczego ??
kurde forum tak szybko chyba nie naprawia teraz jedyna droga pozyskiwania
informacji bedzie gazeta.pl bo nawet na stronie leszka wszystkie informacje sa
z opoznieniem!!

[misza01]

A tu się tyle dzieje. Panic(a) w Lechu, Czesław zostaje... czyżbyśmy zanotowali
powrót synów marnotrawnych na stare śmieci:)

forum pyry - do autorow

[warsau]

moze to cos pomoze ...

The information in this article applies to:
Microsoft Data Access Components 1.5
Microsoft Data Access Components 2.0
Microsoft Data Access Components 2.1
Microsoft Data Access Components 2.1 SP1
Microsoft Data Access Components 2.1 SP2
Microsoft Data Access Components 2.5
Microsoft Data Access Components 2.5 SP1
Microsoft Data Access Components 2.5 SP2
Microsoft Data Access Components 2.6
Microsoft Active Server Pages

This article was previously published under Q306269
SYMPTOMS
When you use ActiveX Data Objects (ADO) or ODBC to connect to a Microsoft
Access database, you may receive the following error message:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access 97 Driver] The Microsoft Jet database engine
cannot open the file '(unknown)'. It is already opened exclusively by another
user, or you need permission to view its data.
CAUSE
There are several causes for this error message:
The account that Microsoft Internet Information Server (IIS) is using (which is
usually IUSR) does not have the correct Windows NT permissions for a file-based
database or for the folder that contains the file.
The file and the data source name are marked as Exclusive.
Another process or user has the Access database open.
The error may be caused by a delegation issue. Check the authentication method
(Basic versus NTLM), if any. If the connection string uses the Universal Naming
Convention (UNC), try to use Basic authentication or an absolute path such as
C:\Mydata\Data.mdb. This problem can occur even if the UNC points to a resource
that is local to the IIS computer.
This error may also occur when you access a local Microsoft Access database
that is linked to a table where the table is in an Access database on a network
server.
RESOLUTION
The following items correspond to the previous list of causes:
Check the permissions on the file and the folder. Make sure that you have the
ability to create and/or destroy any temporary files. Temporary files are
usually created in the same folder as the database, but the file may also be
created in other folders such as the WINNT folder. For additional information
about how to identify which folder does not have the correct permissions and
how to configure temporary files, click the article number below to view the
article in the Microsoft Knowledge Base:

253604 PRB: Microsoft Access Database Connectivity Fails in Active Server Pages

If you use a network path to the database (UNC or mapped drive), check the
permissions on the share, the file, and the folder.
Verify that the file and the data source name (DSN) are not marked as Exclusive.
The "other user" may be Microsoft Visual InterDev. Close any Visual InterDev
projects that contain a data connection to the database.
Simplify. Use a System DSN that uses a local drive letter. If necessary, move
the database to the local drive to test.
Follow the instructions in the following article to work around this problem:

189408 FIX: ASP Fails to Access Network Files Under IIS 4.0 and IIS 5.0


REFERENCES
To check for file access failures, use the Windows NT File Monitor. To download
the File Monitor, see the following Sysinternals Web site:

www.sysinternals.com
Microsoft provides third-party contact information to help you find technical
support. This contact information may change without notice. Microsoft does not
guarantee the accuracy of this third-party contact information.

Last Reviewed: 8/27/2001
Keywords: kbDatabase kbDSupport kbprb KB306269

[Gość: Muldgaard]

Forum już działa !!!!!!!!!!!! :)

[mcdanielo]

znowu cos nie tak... :( . czy moze tylko u mnie???