CNEXT - CATscript error messages - scripting ERR_1002
CNEXT - CATscript error messages - scripting ERR_1002
(OP)
Hi Folks,
I have an error while running the title block script in CATIA V5.The error message reads "CNEXT - CATscript error messages - scripting ERR_1002" as the dialog box of the error message.We tried reinstalling the CATIA VBA but did not help.I found from the blogs that it is an syntax error.It does not happen for all the users and only on specific machines.
Any inputs?
I have an error while running the title block script in CATIA V5.The error message reads "CNEXT - CATscript error messages - scripting ERR_1002" as the dialog box of the error message.We tried reinstalling the CATIA VBA but did not help.I found from the blogs that it is an syntax error.It does not happen for all the users and only on specific machines.
Any inputs?





RE: CNEXT - CATscript error messages - scripting ERR_1002
Which release and OS? Is it CATScript or catvba (why did you reinstall if it is a CATScript)?
Regards
Fernando
https://picasaweb.google.com/102257836106335725208 - Romania
https://picasaweb.google.com/103462806772634246699... - EU
RE: CNEXT - CATscript error messages - scripting ERR_1002
Thanks for your reply.we use teamcentre engineering 7, with catiav5r18,win7 os.it is catscript error only.
RE: CNEXT - CATscript error messages - scripting ERR_1002
so problem is only on some computer and not all user on that computer affected by problem?
I would think this is related to CATSettings.
indocti discant et ament meminisse periti
RE: CNEXT - CATscript error messages - scripting ERR_1002
Thanks for your reply.let me chk the CAT settings and honestly i never thought this might be the issue.
RE: CNEXT - CATscript error messages - scripting ERR_1002
I have replaced the CAT settings and also replaced the folder from which we CATscripts get loaded and still no luck.could u please suggest any thing else?
RE: CNEXT - CATscript error messages - scripting ERR_1002
Adding to this i also got an error "unable to the access the folder from the shared drive" while running the title block macros.we have all the custom macros ( scripts )under program data in local.it is basically a standard title block script used to create the title block.when i run it from the insert ..title block...choose the selected title block it is asking for some field inputs such as sheet no and throws error "cnext- catscript error messages - scripting err_1002".
source : catia drawing texts
line : 2035
column: 4.
RE: CNEXT - CATscript error messages - scripting ERR_1002
indocti discant et ament meminisse periti
RE: CNEXT - CATscript error messages - scripting ERR_1002
I did not get you.It is a standard script used across the company.It is working fine for all others except this machine.
RE: CNEXT - CATscript error messages - scripting ERR_1002
RE: CNEXT - CATscript error messages - scripting ERR_1002
indocti discant et ament meminisse periti
RE: CNEXT - CATscript error messages - scripting ERR_1002
Eric, most probably the CATIA support company will say r18 and Win7...not a good match
By the way, about operating systems...I wasn't able to install on my laptop with Win 10 the 3DExperience platform (cloud) client no mater what I've tried, I could do it only after a complete reset of Win 10 code...
Regards
Fernando
https://picasaweb.google.com/102257836106335725208 - Romania
https://picasaweb.google.com/103462806772634246699... - EU
RE: CNEXT - CATscript error messages - scripting ERR_1002
Thanks for your interest.BTW i am the CATIA support guy working here.I am trying to run cnext /regserver or reinstall.by the way i dont think you nned the code as it is working well for others.it is more over a company standard script for running the title block.
RE: CNEXT - CATscript error messages - scripting ERR_1002
RE: CNEXT - CATscript error messages - scripting ERR_1002
Regards
Fernando
https://picasaweb.google.com/102257836106335725208 - Romania
https://picasaweb.google.com/103462806772634246699... - EU
RE: CNEXT - CATscript error messages - scripting ERR_1002
Thanks a ton for your interest.the regserver command in the command prompt fixed it.there should have been some changes in the registry.i have used this command before but i did nt think about it this time.BTW jenial,i never told that i will not share the script but only meant that i donot see any possibilities of any issues in it.bcoz it is a standard script used across the company.Hope it helps.