Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    42
  • Answers answer
    1
  • Subscribers subscribers
    6
  • Views views
    1091
  • Users 0 members are here
Related
Options

Upgrading iPrint appliance 4.2 to 5.0 or 3.4

Brett Geiger

We are running iPrint appliance 4.2.13 with all the patches. I was trying to migrate to 5.0 or even 23.4 by following the guide to migrate the hard drive over but the nd drive on 4.2 is only 40GB and the recommended is 50 for the newer versions. Expand option on 4.2 is grayed out. We are running this on vmware 8.0.2. 

Parents Reply Children
  • 0 in reply to   

    so in the /root/iprint-iPrintInfo-3.3.0-2024-1125-1453.txt file, what should I be looking for?

  • 0   in reply to 

    Errors on the log files.

  • 0 in reply to   

    Could this be because there were pending jobs on the old server? I think there might of been some pending jobs when I first started the migration. So I am going to try this again, is there a way to see if there are any pending jobs in iManager? I think this time I am going to try migrating to ver 5.0, then update to version 24. Also when migrating over and copying the 2nd HD to the new appliance does this bring over the drivers for the printers? Sorry, for the all the questions now, just want to make sure I'm not messing anything up cause haven't done a migration. 

  • 0   in reply to 

    1. you can see pending jobs in the /psmstatus page

    2. yes, drivers will be migrated. also if you run a backup on the 4.2.13 appliance and you chose to include drivers, there will be also included in the iprintconfig.zip file.

    If you send me the iPrintinfo file and the jetty.txt, i can give them a look

  • 0 in reply to   

    I am starting over with a new migration as there were some scheduled/pending jobs still on the printers when I did the 1st migration, so cleared those up and trying again. 

  • 0   in reply to 

    Thumbsup

  • 0 in reply to   

    When this is starting up, should I be worried about the driver store and print manager daemon failed errors? 

  • 0   in reply to 

    no, this part of the appliance is not configured yet, it will be when you import the iprintconfig.zip file

  • 0 in reply to   

    Fullscreen jetty.txt Download 
    Keystore type: JKS
Keystore provider: SUN

Your keystore contains 2 entries

Alias name: iprint.usd385.org
Creation date: Mar 4, 2024
Entry type: PrivateKeyEntry
Certificate chain length: 2
Certificate[1]:
Owner: CN=*.usd385.org
Issuer: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Serial number: 70e0c68bd58654c5bd1421c3830d534
Valid from: Sun Mar 03 18:00:00 CST 2024 until: Fri Apr 04 18:59:59 CDT 2025
Certificate fingerprints:
	 SHA1: 7D:7D:A8:17:78:D3:40:05:A6:BA:7C:8B:7D:29:04:15:DC:39:CD:BC
	 SHA256: B0:EC:22:01:43:18:E8:6A:B9:8A:CD:DB:FC:64:AC:BE:C5:51:37:EE:E0:53:9A:D5:C3:56:1D:B3:9B:D4:24:3A
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 1.3.6.1.4.1.11129.2.4.2 Criticality=false
0000: 04 82 01 6B 01 69 00 76   00 4E 75 A3 27 5C 9A 10  ...k.i.v.Nu.'\..
0010: C3 38 5B 6C D4 DF 3F 52   EB 1D F0 E0 8E 1B 8D 69  .8[l..?R.......i
0020: C0 B1 FA 64 B1 62 9A 39   DF 00 00 01 8E 09 E7 EF  ...d.b.9........
0030: 6B 00 00 04 03 00 47 30   45 02 20 60 50 1C DB 11  k.....G0E. `P...
0040: 4A 28 A9 D9 E9 19 D8 60   DD A1 37 1C FA 01 4F 5E  J(.....`..7...O^
0050: 03 64 FA 06 1D D7 32 A8   70 1C 06 02 21 00 B5 83  .d....2.p...!...
0060: F2 D0 56 46 0A 0D BB 33   5F 3F 91 B5 38 3A 06 D3  ..VF...3_?..8:..
0070: E7 97 24 9D FD 50 0D 1D   97 E3 01 CF 8F 40 00 77  ..$..P.......@.w
0080: 00 7D 59 1E 12 E1 78 2A   7B 1C 61 67 7C 5E FD F8  ..Y...x*..ag.^..
0090: D0 87 5C 14 A0 4E 95 9E   B9 03 2F D9 0E 8C 2E 79  ..\..N..../....y
00A0: B8 00 00 01 8E 09 E7 EF   B0 00 00 04 03 00 48 30  ..............H0
00B0: 46 02 21 00 92 F4 65 F2   5C 57 9B D0 E2 80 A7 98  F.!...e.\W......
00C0: 33 25 B8 3D 35 66 36 65   3D 1E CB F3 42 30 98 1C  3%.=5f6e=...B0..
00D0: 19 2F 8D 40 02 21 00 E9   C5 8D DD F7 ED 27 92 C3  ./.@.!.......'..
00E0: 96 7D F8 7F F6 9E 53 A4   A9 E0 C2 0E E5 80 AD 1D  ......S.........
00F0: D4 26 4C 0F E4 06 8E 00   76 00 E6 D2 31 63 40 77  .&L.....v...1c@w
0100: 8C C1 10 41 06 D7 71 B9   CE C1 D2 40 F6 96 84 86  ...A..q....@....
0110: FB BA 87 32 1D FD 1E 37   8E 50 00 00 01 8E 09 E7  ...2...7.P......
0120: EF D7 00 00 04 03 00 47   30 45 02 20 0B 09 25 51  .......G0E. ..%Q
0130: 8D 81 C6 DD 55 7A D6 A6   DA B9 97 F8 BA BA 50 A2  ....Uz........P.
0140: D4 CD 01 F5 1D 0F D8 06   FB 48 59 E4 02 21 00 A1  .........HY..!..
0150: CE EB 64 35 0C DF 16 82   29 7A AC 44 57 F8 AB A1  ..d5....)z.DW...
0160: 1D 4C 6F 9E 8E 28 A8 43   C8 04 74 3B 08 07 32     .Lo..(.C..t;..2


#2: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
  [
   accessMethod: ocsp
   accessLocation: URIName: http://status.thawte.com
, 
   accessMethod: caIssuers
   accessLocation: URIName: http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
]
]

#3: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: A5 8C FE 32 CC EB 0F 2C   D4 19 C6 08 B8 00 24 88  ...2...,......$.
0010: 5D C3 C5 B7                                        ]...
]
]

#4: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
  CA:false
  PathLen: undefined
]

#5: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
  [DistributionPoint:
     [URIName: http://cdp.thawte.com/ThawteTLSRSACAG1.crl]
]]

#6: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
  [CertificatePolicyId: [2.23.140.1.2.1]
[PolicyQualifierInfo: [
  qualifierID: 1.3.6.1.5.5.7.2.1
  qualifier: 0000: 16 1B 68 74 74 70 3A 2F   2F 77 77 77 2E 64 69 67  ..http://www.dig
0010: 69 63 65 72 74 2E 63 6F   6D 2F 43 50 53           icert.com/CPS

]]  ]
]

#7: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
  serverAuth
  clientAuth
]

#8: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
  DigitalSignature
  Key_Encipherment
]

#9: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
  DNSName: *.usd385.org
  DNSName: usd385.org
]

#10: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: F0 29 10 7F 53 9E C6 A7   9E 35 7E 7A 19 84 5C 8C  .)..S....5.z..\.
0010: 2F CA C7 30                                        /..0
]
]

Certificate[2]:
Owner: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Serial number: 90ee8c5de5bfa62d2ae2ff7097c4857
Valid from: Thu Nov 02 07:24:25 CDT 2017 until: Tue Nov 02 07:24:25 CDT 2027
Certificate fingerprints:
	 SHA1: C9:FE:FC:76:3D:95:48:B4:87:69:6F:04:7A:CB:A0:AB:E4:5C:7B:C1
	 SHA256: 4B:CC:5E:23:4F:E8:1E:DE:4E:AF:88:3A:A1:9C:31:33:5B:0B:26:E8:5E:06:6B:99:45:E4:CB:61:53:EB:20:C2
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
  [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.digicert.com
]
]

#2: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 4E 22 54 20 18 95 E6 E3   6E E6 0F FA FA B9 12 ED  N"T ....n.......
0010: 06 17 8F 39                                        ...9
]
]

#3: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
  CA:true
  PathLen:0
]

#4: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
  [DistributionPoint:
     [URIName: http://crl3.digicert.com/DigiCertGlobalRootG2.crl]
]]

#5: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
  [CertificatePolicyId: [2.5.29.32.0]
[PolicyQualifierInfo: [
  qualifierID: 1.3.6.1.5.5.7.2.1
  qualifier: 0000: 16 1C 68 74 74 70 73 3A   2F 2F 77 77 77 2E 64 69  ..https://www.di
0010: 67 69 63 65 72 74 2E 63   6F 6D 2F 43 50 53        gicert.com/CPS

]]  ]
]

#6: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
  serverAuth
  clientAuth
]

#7: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
  DigitalSignature
  Key_CertSign
  Crl_Sign
]

#8: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: A5 8C FE 32 CC EB 0F 2C   D4 19 C6 08 B8 00 24 88  ...2...,......$.
0010: 5D C3 C5 B7                                        ]...
]
]



*******************************************
*******************************************


Alias name: org_ca
Creation date: Nov 26, 2024
Entry type: trustedCertEntry

Owner: O=APPLIANCE_1616619080, OU=Organizational CA
Issuer: O=APPLIANCE_1616619080, OU=Organizational CA
Serial number: 5a22948693d29a8ff8d2739f2461f350006463fc
Valid from: Mon Mar 22 15:51:46 CDT 2021 until: Sat Mar 22 15:51:46 CDT 2031
Certificate fingerprints:
	 SHA1: 7A:E3:10:40:FD:2D:E2:65:8D:95:99:7A:3E:AC:7F:15:DF:17:A2:29
	 SHA256: BF:2D:EF:A9:28:29:B4:E3:EF:05:C5:1B:80:A4:52:A9:D8:46:B1:CF:9F:CA:32:48:6D:41:3E:D0:05:90:8C:58
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 2.16.840.1.113719.1.9.4.1 Criticality=false
0000: 30 82 01 B7 04 02 01 00   01 01 FF 13 1D 4E 6F 76  0............Nov
0010: 65 6C 6C 20 53 65 63 75   72 69 74 79 20 41 74 74  ell Security Att
0020: 72 69 62 75 74 65 28 74   6D 29 16 43 68 74 74 70  ribute(tm).Chttp
0030: 3A 2F 2F 64 65 76 65 6C   6F 70 65 72 2E 6E 6F 76  ://developer.nov
0040: 65 6C 6C 2E 63 6F 6D 2F   72 65 70 6F 73 69 74 6F  ell.com/reposito
0050: 72 79 2F 61 74 74 72 69   62 75 74 65 73 2F 63 65  ry/attributes/ce
0060: 72 74 61 74 74 72 73 5F   76 31 30 2E 68 74 6D 30  rtattrs_v10.htm0
0070: 82 01 48 A0 1A 01 01 00   30 08 30 06 02 01 01 02  ..H.....0.0.....
0080: 01 46 30 08 30 06 02 01   01 02 01 0A 02 01 69 A1  .F0.0.........i.
0090: 1A 01 01 00 30 08 30 06   02 01 01 02 01 00 30 08  ....0.0.......0.
00A0: 30 06 02 01 01 02 01 00   02 01 00 A2 06 02 01 18  0...............
00B0: 01 01 FF A3 82 01 04 A0   58 02 01 02 02 02 00 FF  ........X.......
00C0: 02 01 00 03 0D 00 80 00   00 00 00 00 00 00 00 00  ................
00D0: 00 00 03 09 00 80 00 00   00 00 00 00 00 30 18 30  .............0.0
00E0: 10 02 01 00 02 08 7F FF   FF FF FF FF FF FF 01 01  ................
00F0: 00 02 04 06 F0 DF 48 30   18 30 10 02 01 00 02 08  ......H0.0......
0100: 7F FF FF FF FF FF FF FF   01 01 00 02 04 06 F0 DF  ................
0110: 48 A1 58 02 01 02 02 02   00 FF 02 01 00 03 0D 00  H.X.............
0120: 40 00 00 00 00 00 00 00   00 00 00 00 03 09 00 40  @..............@
0130: 00 00 00 00 00 00 00 30   18 30 10 02 01 00 02 08  .......0.0......
0140: 7F FF FF FF FF FF FF FF   01 01 00 02 04 11 FF AF  ................
0150: 89 30 18 30 10 02 01 00   02 08 7F FF FF FF FF FF  .0.0............
0160: FF FF 01 01 00 02 04 11   FF AF 89 A2 4E 30 4C 02  ............N0L.
0170: 01 02 02 02 00 FF 02 01   00 03 0D 00 80 FF FF FF  ................
0180: FF FF FF FF FF FF FF FF   03 09 00 80 FF FF FF FF  ................
0190: FF FF FF 30 12 30 10 02   01 00 02 08 7F FF FF FF  ...0.0..........
01A0: FF FF FF FF 01 01 FF 30   12 30 10 02 01 00 02 08  .......0.0......
01B0: 7F FF FF FF FF FF FF FF   01 01 FF                 ...........


#2: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 3A 0D C3 0F AA FA 45 51   67 53 1F 8F 31 E5 E8 4C  :.....EQgS..1..L
0010: 59 F4 DA A3                                        Y...
]
]

#3: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
  CA:true
  PathLen:2147483647
]

#4: ObjectId: 2.5.29.15 Criticality=false
KeyUsage [
  Key_CertSign
  Crl_Sign
]

#5: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 3A 0D C3 0F AA FA 45 51   67 53 1F 8F 31 E5 E8 4C  :.....EQgS..1..L
0010: 59 F4 DA A3                                        Y...
]
]



*******************************************
*******************************************

    iprint-iPrintInfo-3.3.0-2024-1126-0914.txt

    So attached are those 2 logs. This is a new server that was just done with following the migration process of attaching the old extra HD from the old server to this one. This is also only on version 5.0 with all the latest patches, but it gives me the option to update to version 24. I can do that if needed but wanted to see if just going to version 5 worked. I am still getting the submission failed when trying to print.

  • 0   in reply to 

    1. Certs look fine
    2. If you go to the web interface, port 9443, then appliance configuration and then license, do you have a valid one? The current one is from version 3.
    3. The /var/opt/novell/iprintmobile/jobs/ is too full. Stop mobile services and delete them. Restart mobile services
    4. You have printers with the papercut gateway. How are you sending the print job to print? what printer name?


    You see this error:

    11/26/2024 09:14:21 AM, Operation Print:,
    Error: 506D002D - accounting service error,

    probably the submitting failure is coming from papercut

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.