Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

Executing a second time a DELIVER leads to delete fodler in the stream (reproduced in 2009r2.10 and in 12.2.2.3)

c:\JM\LIV\doc\titi.c c) from the console view of the desktop client, run this DELIVER statement : DELIVER /DIRECTORY="C:\JM\LIV" /ALL /ADD /UPDATE /DELETE /WORKSET="PAYROLL:JM" /USER_DIRECTORY="C:\JM\LIV" /COMMENT="Test"

Similar Answers

Killer Import Error: Executing SQL directly; no cursor. Incorrect syntax near the keyword 'order' doing import from db

Incorrect syntax near the keyword 'order'. Statement (s) could not be prepared. (ODBC native: State:01000,Native:16954,Origin:[Microsoft][SQL Server Native Client 10.0][SQL Server]

SLA Notifications display in the Admin portal after Promotion

Intermittently SLA's claused not showing

Occasional user cannot see SLA status on an item they can see

Invalid procedure call or argument when working with SLA reports

Intermittent issues with SLA's not showing in the Application Administrator

Create Unique Index statement fails during database upgrade

Even deleted and expired SLA's continue to appear in the SLA reports

View All Items role privilege is ignored for notifications - also in SSM SLA reports might show incorrect items

Pages [Next]

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance