Release notes for 1.9.3.5

[George Kowalski]

I went to download the latest 1.9.X image and received 1.9.3.5 . I Don't see the release notes for this https://wiki.xnat.org/documentation/xnat-1-9-releases . What changed ? 

[George Kowalski]

I ask as pushing images to this version using teh xnat desktop client  ( just upgraded from 1.9.2.1 ) the images get stuck in the pre-archive instead of getting archived automatically. 

[Will Horton]

Hello George, 

Here are the release notes for XNAT 1.9.3.5. https://wiki.xnat.org/documentation/xnat-1-9-3-5-release-notes. This release was primarily focused on search performance improvements and shouldn't have affected import behavior. 

However, if you're upgrading from XNAT 1.9.2.1, the changes in 1.9.3 might be most pertinent to walk through and rule out any change that you're seeing. https://wiki.xnat.org/documentation/xnat-1-9-3-release-notes. 

Have you tried uploading that same data to the same project using the compressed uploader? I'm curious if it also lands in the Prearchive. 

Regards,

Will 

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/355c1047-5731-4c76-8740-3344d5eafa36n%40googlegroups.com.

--

Will Horton

Director of Product

 wi...@xnatworks.io

 xnatworks.io | Find us on LinkedIn! 

[George Kowalski]

I will be downgrading my jar file to the 1.9.3 and starting from there to test the versions and see where the issue starts. 

As I am poking around I see in my latest xdat.log file : 

```

2026-05-18 14:18:56,060 [main] ERROR org.nrg.xdat.servlet.XDATServlet - Preparing create SQL and got 90 optional SQL statements. Please review this optional SQL and consider executing it if required:

Optional SQL:


--Database column xnat_addfield.addfield type mis-match ('TEXT'!='varchar').

----Unable to resolve type mis-match for the following reason(s).

----Please review these factors before uncommenting this code.

----680 row(s) contain values.

-- -- Start transaction
-- BEGIN TRANSACTION;
--
-- -- Remove dependencies so they don't block altering columns
-- SELECT dependencies_save_and_drop('xnat_addfield');
--
-- -- Fix xnat_addfield_history table.
-- ALTER TABLE xnat_addfield_history ADD COLUMN addfield_cp TEXT;
--
-- UPDATE xnat_addfield_history SET addfield_cp = CAST(addfield AS TEXT);
--
-- ALTER TABLE xnat_addfield_history DROP COLUMN addfield;
--
-- ALTER TABLE xnat_addfield_history RENAME COLUMN addfield_cp TO addfield;
--
-- CREATE OR REPLACE FUNCTION after_update_xnat_addfield()
--     RETURNS TRIGGER
-- AS
-- $_$
-- BEGIN
--     RETURN NULL;
-- END;
-- $_$
--     LANGUAGE plpgsql VOLATILE;
--
-- -- Fix xnat_addfield table.
-- ALTER TABLE xnat_addfield ADD COLUMN addfield_cp TEXT;
--
-- UPDATE xnat_addfield SET addfield_cp = CAST(addfield AS TEXT);
--
-- ALTER TABLE xnat_addfield DROP COLUMN addfield;
--
-- ALTER TABLE xnat_addfield RENAME COLUMN addfield_cp TO addfield;
--
-- -- Restore dependencies
-- SELECT dependencies_restore('xnat_addfield');
--
-- -- Commit transaction
-- COMMIT;
--

--Database column xnat_addfield.addfield is now required.
--ALTER TABLE xnat_addfield  ALTER COLUMN addfield SET NOT NULL;

--Database column xnat_resource.uri is now required.
--ALTER TABLE xnat_resource  ALTER COLUMN uri SET NOT NULL;

--Database column xnat_ctscandata.parameters_options type mis-match ('TEXT'!='varchar').

----Unable to resolve type mis-match for the following reason(s).

----Please review these factors before uncommenting this code.

----21461 row(s) contain values.

-- -- Start transaction
-- BEGIN TRANSACTION;
--
-- -- Remove dependencies so they don't block altering columns
-- SELECT dependencies_save_and_drop('xnat_ctscandata');
--
-- -- Fix xnat_ctscandata_history table.
-- ALTER TABLE xnat_ctscandata_history ADD COLUMN parameters_options_cp TEXT;
--
-- UPDATE xnat_ctscandata_history SET parameters_options_cp = CAST(parameters_options AS TEXT);
--
-- ALTER TABLE xnat_ctscandata_history DROP COLUMN parameters_options;
--
-- ALTER TABLE xnat_ctscandata_history RENAME COLUMN parameters_options_cp TO parameters_options;
--
-- CREATE OR REPLACE FUNCTION after_update_xnat_ctscandata()
--     RETURNS TRIGGER
-- AS
-- $_$
-- BEGIN
--     RETURN NULL;
-- END;
-- $_$
--     LANGUAGE plpgsql VOLATILE;
--
-- -- Fix xnat_ctscandata table.
-- ALTER TABLE xnat_ctscandata ADD COLUMN parameters_options_cp TEXT;
--
-- UPDATE xnat_ctscandata SET parameters_options_cp = CAST(parameters_options AS TEXT);
--
-- ALTER TABLE xnat_ctscandata DROP COLUMN parameters_options;
--
-- ALTER TABLE xnat_ctscandata RENAME COLUMN parameters_options_cp TO parameters_options;
--
-- -- Restore dependencies
-- SELECT dependencies_restore('xnat_ctscandata');
--
-- -- Commit transaction
-- COMMIT;

```

What is this all about ? Optional SQL ? 

G

[George Kowalski]

As for uploading via the "compressed uploader" , not sure what that is as I only use the XNAT Desktop client. 

G

[George Kowalski]

went from bad to worse. Bounced tomcat ( didn't change  anything ) and now I see this in the xdat.log : 

```

2026-05-26 15:07:18,138 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-4] WARN  org.nrg.xnat.utils.XnatHttpUtils - Checked for password encoding upgrade required, but couldn't find the username d0e5f009-6440-4408-97b2-b327df89ad69
2026-05-26 15:17:41,654 [main] ERROR org.nrg.xdat.servlet.XDATServlet - Preparing create SQL and got 90 optional SQL statements. Please review this optional SQL and consider executing it if required:

Optional SQL:


--Database column xnat_addfield.addfield type mis-match ('TEXT'!='varchar').

----Unable to resolve type mis-match for the following reason(s).

----Please review these factors before uncommenting this code.

----680 row(s) contain values.

... stuff deleted .. 

```

and now the login screen comes up , but any userid / password I enter gives an error screen  : 

Bad Request

Your browser sent a request that this server could not understand.

Looks like a copy of prod back to dev and reinstall of the jar. 

[Will Horton]

George, 

The message you are seeing in xdat.log related to the "optional SQL" refers to a change in the CT Scan history field, which needs to be altered from "VARCHAR" to "TEXT" on some systems to accommodate longer strings. This was actually introduced in XNAT 1.9.2 (in ticket XNAT-8205), so if you were previously running XNAT 1.9.2.1 before you started this upgrade, the message was probably there on startup as well. 

With regard to the error you're seeing on login, I think this xdat log statement is probably a red herring. I'm hoping someone else in our group can comment on that error message. It sounds like it could possibly be a proxy issue or something else that is interrupting the sending of your credentials back to the XNAT server. 

Regarding my suggestion to use the "compressed uploader", I was referring to the XNAT UI. Once we get past this login bug, you would be able to go to the Upload > Images > Compressed Uploader and upload a zip file containing the DICOM files you're attempting to upload via the Desktop Client. There is documentation here: https://wiki.xnat.org/documentation/using-the-compressed-image-uploader. 

Regards,

Will 

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/4b4a6fe1-b629-4cd6-8109-c782bc700a47n%40googlegroups.com.

[George Kowalski]

Yea the whole system horked up after I tried to upload a zip file with that compressed uploader. Rolling back the DB .