Sage 100

What would make this fail? Set oScript = CreateObject (""ProvideX.Script"") This is a script by a shipping vendor and they say it's because pvcom has an issue, but I've run pvxcom several times. What EXACTLY could cause this to fail? (PS - If you have never worked with OzLink, do NOT plan on starting.)

not sure if it will make a difference but have you tried running regcomm.bat?

Anything is worth a shot.

I've worked with OzLink. If Premium or Advanced, their script run on the server; otherwise, the workstation (you probable know this). Their scripts generally use the registry settings to determine the path to the MAS90 folder. I've had better success just ""hard coding"" the UNC path. Their develop and support staff are spread too thin to make a reliable solution.

@Myron - so you feel my pain. The thing is, it appears to be finding the correct path. I'm wondering if permissions are at play here (ugh). This is a client with a new server and a 2016 upgrade we are testing on the new server. Ozlink is working on 2013 on the old server, just not on this new server.

You could try a generic BOI script for testing permissions. One the Alnoor has shared or the add GL account from the BOI training.

Run the OITest.exe from the Home directory Myron mentioned. If it fails too check if the Allow External Access flag in Company Maintenance is unchecked. Or just check that first.

Ahem. OzLink is officially on my DumbAss list. It wasn't a pvxcom issue, they were just too lazy to actually determine what the error was and just threw it into that area. The problem was on another line of the script - couldn't find THEIR OWN .INI file because they didn't have THEIR OWN FOLDER in the same place on both servers. If they show up at Summit, someone will have to hold me back or I will totally shred their salesperson(s).

OITest.exe from the Home directory tells me ""set company failed"" even though ""Allow external access"" is checked for that company. Other considerations?