Error creating a pdf on a NSS volume OES2 sp2

[dsmi87dgf]

Hoping someone has seen this and found a fix.
Users create a pdf using Acrobat 9. The option in the pdf printer checked is "view adobe pdf results". The user gets an error saving to a NSS volume on OES2 sp2 but not locally, on Netware 6.5 NSS or a Windows share. The error is
acrobat could not open 'filename.pdf' because it is either not a supported file type or because the file has been damaged.

We tried with file commit on and off at both the server and workstation. File cache is off. Thanks for any leads.

[kjhurni]

What client OS and Novell Client are you using? (assuming you're using NCP)

ARe you also using CIFS?

Do you have cross-protocol locks enabled?

Is oplocking enabled/disabled on the OES2 server?

[PatMueller]

We are experiencing something very similar with a different PDF program we
use for scanning (happens to be eCopy). Does the resulting file get created
with a zero file size per chance? We find that the PDF is still intact in
the Windows temp folder and the NSS file gets created but content/data never
actually gets transferred to the NSS vol. Is this a consistent problem for
you or occasional and seemingly random, here it is unpredictable. We also
see a similar issue with a totally different application (not PDF files)
leading me to think it is not just a pdf issue or an application issue. We
worked with Novell support for a bit without success and they seemed to have
sidelined/closed our SR. I must say that we seem to have lessened the
number of incidences by making sure that purgeable files stays well below
10%, but that did not eliminate the problem. Any ideas or help is most
appreciated--We are OES2 SP2 and to answer the questions posed:

What client OS and Novell Client are you using? (assuming you're using
NCP)--Win XP SP3, Client 4.91.5.20080922, we went to File Caching=Off and
Fie Commit=On as support suggestioned which affects performance terribly.

ARe you also using CIFS? NO

Do you have cross-protocol locks enabled? NO, NSS vols only

Is oplocking enabled/disabled on the OES2 server? set to 2, enabled
"kjhurni" <kjhurni@no-mx.forums.novell.com> wrote in message
news:kjhurni.4suuu2@no-mx.forums.novell.com...
>
> What client OS and Novell Client are you using? (assuming you're using
> NCP)
>
> ARe you also using CIFS?
>
> Do you have cross-protocol locks enabled?
>
> Is oplocking enabled/disabled on the OES2 server?
>
>
> --
> The opinions expressed are my own.
> Check out my OES2 Guides:
> Installing OES2 SP2:
> http://www.novell.com/communities/node/11600/oes2-sp2-installation-guide
> Upgrading to OES2 with ID Transfer:
> http://www.novell.com/communities/node/11601/oes2-sp2-migration-guide-transfer-id-scenarios
> GroupWise Migration with OES2 ID Transfer:
> http://www.novell.com/communities/node/11602/groupwise-migration-netware-oes2-sp2-transfer-id
> ------------------------------------------------------------------------
> kjhurni's Profile: http://forums.novell.com/member.php?userid=734
> View this thread: http://forums.novell.com/showthread.php?t=437587
>

[dsmi87dgf]

Win 7 64, Novell Client 2 Sp1 for win 7 ir5
CIFS is not installed
Cross protocol locks is off
Oplock support is off
Cheers.

[kjhurni]

hmmm, have either of you taken a LAN trace from both the workstation, and the OES2 server, along with enabling NCP debug mode for logs?

I'm thinking that the problem is with NCP (if I had to guess) vs. NSS.

But that's just a guess.

[jmarton2]

dsmi87dgf wrote:

>
> Hoping someone has seen this and found a fix.
> Users create a pdf using Acrobat 9. The option in the pdf printer
> checked is "view adobe pdf results". The user gets an error saving to
> a NSS volume on OES2 sp2 but not locally, on Netware 6.5 NSS or a
> Windows share. The error is
> acrobat could not open 'filename.pdf' because it is either not a
> supported file type or because the file has been damaged.
>
> We tried with file commit on and off at both the server and
> workstation. File cache is off. Thanks for any leads.

We were getting this as well with Acrobat 10, and OES2 SP2 using XP SP3
clients. Tried even the 4.91 SP5 IR1 Novell Client to no avail.
Ultimately, upgrading the server to OES2 SP3 appeared to resolve the
issue.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

[PatMueller]

My consutant and I did do a LAN trace a while back, nothing of note that we
could find. We even sent some to Novell as I recall and there was no
resolution.
I have not applied SP3 yet based on consultant advice of some serious
problems with it at another client, but that was when first released, and I
saw it has been updated. General consensus is it is OK now? Did all of you
have this as an intermitant issue, or where you able to re-create the
problem at will? Would be great if that is the fix since I have been
unsuccessful with assorted tasks like upgrading an application because files
were not created properly and other similar acting issues.
"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote in message
news:riXtp.6$TS3.3@kovat.provo.novell.com...
> dsmi87dgf wrote:
>
>>
>> Hoping someone has seen this and found a fix.
>> Users create a pdf using Acrobat 9. The option in the pdf printer
>> checked is "view adobe pdf results". The user gets an error saving to
>> a NSS volume on OES2 sp2 but not locally, on Netware 6.5 NSS or a
>> Windows share. The error is
>> acrobat could not open 'filename.pdf' because it is either not a
>> supported file type or because the file has been damaged.
>>
>> We tried with file commit on and off at both the server and
>> workstation. File cache is off. Thanks for any leads.
>
> We were getting this as well with Acrobat 10, and OES2 SP2 using XP SP3
> clients. Tried even the 4.91 SP5 IR1 Novell Client to no avail.
> Ultimately, upgrading the server to OES2 SP3 appeared to resolve the
> issue.
>
> --
> Novell Knowledge Partner
> Enhancement Requests: http://www.novell.com/rms

[jmarton2]

PatM wrote:

> My consutant and I did do a LAN trace a while back, nothing of note
> that we could find. We even sent some to Novell as I recall and
> there was no resolution. I have not applied SP3 yet based on
> consultant advice of some serious problems with it at another client,
> but that was when first released, and I saw it has been updated.
> General consensus is it is OK now? Did all of you have this as an
> intermitant issue, or where you able to re-create the problem at
> will? Would be great if that is the fix since I have been
> unsuccessful with assorted tasks like upgrading an application
> because files were not created properly and other similar acting
> issues.

The user who reported the issue could duplicate it at will with OES2
SP2. AFter moving to OES2 SP3, she hasn't had it happen at all.

There were some issues with SP3 and the performance of opening files,
but that was only with the April maintenance update for SP3. The
initial release (what we're still using) was fine. The April
maintenance has been re-released to address teh performance issues.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

[dsmi87dgf]

I applied SP3 last night but the issue remains. Can someone please post their NCP settings here from a server that does not show this problem?

[jmarton2]

dsmi87dgf wrote:

> I applied SP3 last night but the issue remains. Can someone please
> post their NCP settings here from a server that does not show this
> problem?

My ncpserv.conf is pretty plain. Just has these three entries:

VOLUME sys /usr/novell/sys
NCP_FILE_SERVER_NAME [server name]
CROSS_PROTOCOL_LOCKS 1

Do you have a cross protocol locks setting in yours?

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

[dsmi87dgf]

I don't think it's cross protocol locks. I am comparing the settings (Norm > Manage NCP Services > Manage server) from our two OES2 SP3 file servers. Both of the servers have CPL at 0
We have to turn it off for lotus notes.
On the newer SP3 server (it's a VM) the pdf error doesn't occur. On the physical, recently patched server, the problem continues.

Could you post what you have in Norm > Manage NCP Services > Manage server?

[jmarton2]

dsmi87dgf wrote:

> Could you post what you have in Norm > Manage NCP Services > Manage
> server?

AUDITING_SUPPORT 0
COMMIT_FILE 0
CROSS_PROTOCOL_LOCKS 1
DISABLE_BROADCAST 0
DUPLICATE_SHADOW_FILE_ACTION 0
DUPLICATE_SHADOW_FILE_BROADCAST 1
EXECUTE_ATTRIBUTE_SUPPORT 1
FIRST_WATCHDOG_PACKET 0
KEEP_NSS_FILE_DELETOR_IDS 1
LOCAL_CODE_PAGE CP437
LOG_CACHE_STATISTICS 0
LOG_IDBROKER_ERRORS 0
LOG_LEVEL WARN
LOG_LOCK_STATISTICS 0
LOG_MEMORY_STATISTICS 0
MAXIMUM_CACHED_FILES_PER_SUBDIRECTORY 10240
MAXIMUM_CACHED_FILES_PER_VOLUME 256000
MAXIMUM_CACHED_SUBDIRECTORIES_PER_VOLUME 102400
MAXIMUM_FILE_LOCKS_PER_CONNECTION 1000
MAXIMUM_LAZY_CLOSE_FILES 4096
OPLOCK_SUPPORT_LEVEL 2
REPLICATE_PRIMARY_TREE_TO_SHADOW 0
SENDFILE_SUPPORT 0
SHIFT_ACCESSED_SHADOW_FILES 0
SHIFT_DAYS_SINCE_LAST_ACCESS 1
SHIFT_MODIFIED_SHADOW_FILES 1
SYNC_TRUSTEES_TO_NSS_AT_VOLUME_MOUNT 0
VOLUME_EMPTY_WARN_USERS 1
VOLUME_GONE_WARN_USERS 1
VOLUME_LOW_WARNING_RESET_THRESHOLD 128
VOLUME_LOW_WARNING_THRESHOLD 64
VOLUME_LOW_WARN_USERS 1

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

[PatMueller]

Did anyone ever figure out if any of these settings were implicated in this
issue? If so, can you please post findings? Thanks.
"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote in message
news:Cxiup.304$Fl7.266@kovat.provo.novell.com...
> dsmi87dgf wrote:
>
>> Could you post what you have in Norm > Manage NCP Services > Manage
>> server?
>
> AUDITING_SUPPORT 0
> COMMIT_FILE 0
> CROSS_PROTOCOL_LOCKS 1
> DISABLE_BROADCAST 0
> DUPLICATE_SHADOW_FILE_ACTION 0
> DUPLICATE_SHADOW_FILE_BROADCAST 1
> EXECUTE_ATTRIBUTE_SUPPORT 1
> FIRST_WATCHDOG_PACKET 0
> KEEP_NSS_FILE_DELETOR_IDS 1
> LOCAL_CODE_PAGE CP437
> LOG_CACHE_STATISTICS 0
> LOG_IDBROKER_ERRORS 0
> LOG_LEVEL WARN
> LOG_LOCK_STATISTICS 0
> LOG_MEMORY_STATISTICS 0
> MAXIMUM_CACHED_FILES_PER_SUBDIRECTORY 10240
> MAXIMUM_CACHED_FILES_PER_VOLUME 256000
> MAXIMUM_CACHED_SUBDIRECTORIES_PER_VOLUME 102400
> MAXIMUM_FILE_LOCKS_PER_CONNECTION 1000
> MAXIMUM_LAZY_CLOSE_FILES 4096
> OPLOCK_SUPPORT_LEVEL 2
> REPLICATE_PRIMARY_TREE_TO_SHADOW 0
> SENDFILE_SUPPORT 0
> SHIFT_ACCESSED_SHADOW_FILES 0
> SHIFT_DAYS_SINCE_LAST_ACCESS 1
> SHIFT_MODIFIED_SHADOW_FILES 1
> SYNC_TRUSTEES_TO_NSS_AT_VOLUME_MOUNT 0
> VOLUME_EMPTY_WARN_USERS 1
> VOLUME_GONE_WARN_USERS 1
> VOLUME_LOW_WARNING_RESET_THRESHOLD 128
> VOLUME_LOW_WARNING_THRESHOLD 64
> VOLUME_LOW_WARN_USERS 1
>
> --
> Novell Knowledge Partner
> Enhancement Requests: http://www.novell.com/rms

[dsmi87dgf]

I just migrated the data to a new SP3 server. so far so good.